Joomla 3.7 stable version.
By Rick Kasparek on Thursday, 23 February 2017
Posted in General Issues
Replies 5
Likes 0
Views 193
Votes 0
Not an issue but a question regarding the expected release of Joomla 3.7 stable version.

With the new release, I understand Joomla has added custom fields to the core - is StackIdeas intending to take advantage of the framework to merge EasySocial custom fields with the underlying Joomla framework in 3.7?

What kind of impact will this make to users of EasySocial?
Sure, we will double check with all our existing product in Joomla 3.7.
Arlex Wong
·
Friday, 24 February 2017 15:26
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm assuming com_finder (Smart Search) will have a method for searching the new custom fields. Not sure if EasySocial's search would have to be modified to work with this. Assuming it works, developers could then write a simple PHP script that checks the Profile type and display relevant content from articles that use a specific custom field via AJAX. In other words this would unload some really outstanding possibilities to tailor content to users within some very specific niche's. And if there was a way to map that content in the custom fields, suddenly showing local articles automatically would be a breeze!

Joomla 3.7 beta 3 was released 2 days ago. Seems like we are getting close to stable.
Josh Lewis
·
Friday, 24 February 2017 02:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Unfortunately there is no way right now to use the fields from Joomla. The functionality of these fields are pretty restricted and not something that we could integrate with EasySocial's field.

If there is a possibility, we'll definitely find a way to ride on the custom fields that Joomla has in the future
Mark
·
Friday, 24 February 2017 11:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you for the replies! I just wanted to make sure that when 3.7 is released, we wont see anything broken in EasySocial, or EasyDiscussions... you folks ROCK!
Rick Kasparek
·
Friday, 24 February 2017 11:44
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post