I have been thinking that Enfold has served it purpose on a couple sites and want to possibly move on with a new theme. The inherent problem being that with the framework that is built all the shortcodes would be lost.
What are your suggestions for this? I would guess that creating a plug-in based off all the supplied shortcodes would work for short term fix?
That would be the best way to do it. We will eventually roll out a plugin to port the shortcodes to have some support for secondary use but for right now we don’t have anything available to make the transition easier.
Thanks for the reply. So would I just pull-in the code for shortcodes from config-templatebuilder/avia-shortcodes directory? I know enough PHP to do some damage but am not up-to-speed on using classes.
Would it be easier or even possible to have a plug-in that does an include call of those files or will they need to be disected into different individual functions?
It will be quite a bit more complicated than that unfortunately. As WordPress the community has gotten smarter so have the high end themes. So in this case you are working with classes and extending classes to go beyond the basic WordPress shortcode output.
Off hand I couldn’t even give a good description of how to pull everything out into a shortocde but given a few hours and full access to the theme files a good developer should be able to get you set to re-create the shortcodes in a way that will output them and ready for css clean up.
Basically going through and looking at the function shortcode_handler attributes then creating a shortcode to follow suit and adding it in is how I would do it. You could try it the other way around and include the aviaShortCodeTemplate class and the avia-shortcodes though I don’t have as much experience with oop with php.
The topic ‘Moving away from Enfold’ is closed to new replies.