SP PageBuilder Conflict With ZOO
G
Geoff
I have just become aware of this... it is causing a major issue for us with SP PageBuilder conflicting with the very popular ZOO component. Can it be resolved quickly? Excerpt from ZOO support ticket...
(ZOO Support)
The only way prevent ZOO from being broken in the backend while SP PageBuilder is installed, would be to navigate to System > Manage > Extensions, into the filter field insert System - SP PageBuilder, click on the search icon, tick Image System - SP PageBuilder, and click on the button "Disable" in the toolbar.
Once you have done what you wanted to do in ZOO, go to System > Manage > Extensions again, tick Image System - SP PageBuilder, and click on the button "Enable" in the toolbar.
FYI:
Unfortunately, both SP PageBuilder and ZOO use an identically named class ApplicationHelper without a "namespace", which causes a conflict. YOOtheme is aware of the problem, but there is no easy solution.
After having the Joomshaper Support Agent Review the issue, they stated, "Please contact the Zoo developer to check the issue. SP Page Builder runs well with Zoo. But Zoo is not running well. So, please check it with their developer."
Differently put: SP Page Builder interferes where it shouldn't and breaks ZOO — not the other way round. But a "blame game" won't lead anywhere. 😉
Thanks. Please... ? Geoff
16 Answers
Order by
Oldest
Ofi Khan
Accepted AnswerHello Geoff
Thanks for bringing up the issue. I have got the old forum post and forwarded it to the development team. They will review it and if possible will make a change to support Yootheme Zoo. Let's hope for the best.
Best regards
Ofi Khan
Accepted AnswerYou are welcome 😊
Sorry, it has not reviewed yet. I have set high priority for your request.
CK
craig kennedy
Accepted AnswerI know this is old, bt I have had this issue for a while now. I just installed a new fresh copy of Joomla 5.4, installed the latest Zoo, SPPB and same issue. I then uninstalled SPPB Extracted the zip file for SPPB. Ran a scan looking for all entries inside each file of SPPB for "ApplicationHelper", and replaced each entry (in a single hit) with "ApplicationHelperspb" Saved it all. I then renamed the file in admin/components/com_sppagebuilder/editor/helpers to "ApplicationHelperspb"
Re-zipped it all up, and installed this into the new site, and now both are running side by side without issue
BV
Benedikt Vitt
Accepted AnswerIt would be great if the renaming or use of namespace can be implemented in the next Version. We have also Problems with Alphaindex in Zoo because of the same Naming of the helper.
Ofi Khan
Accepted AnswerPlease share zoo component as ZIP in the hidden content for testing purpose. I will check the package and discuss it with the developer team. If possible, then we will change the naming of the helper class.
CK
craig kennedy
Accepted AnswerI have attached the installable zip with the modifications, tested on 5.4.3 zoo with no issues at all, able to use Zoo, add edir items, categories etc, and also SPPageBuilder.
CK
craig kennedy
Accepted AnswerJust to add to this, I have been testing and using this now in a live working site, the working site has not been upgraded to the latest 5.4 version, so I can say with some 99% confidence there are no issues with it at all
Ofi Khan
Accepted AnswerThanks for your update. The developer team on a holiday for 2 weeks. I will share your version with them. They will check and fix it on our version if needed.
CK
craig kennedy
Accepted AnswerITs been a while now, and I want to know if I still need to modify your code to solve this or if your last release has the fix in it already?
CK
craig kennedy
Accepted AnswerYup, been a while and still you have not made this very simepl fix to resolve many users issues.!!!!!
Ofi Khan
Accepted AnswerApology for the delay. I have asked the developer team to consider this feature suggestion.
Ofi Khan
Accepted AnswerThe developer wanted to investigate the issue. Could you please share Zoo installable zip file with us? Also, share exactly where the issue is happening. Thanks for your patience.
CK
craig kennedy
Accepted AnswerI am not sure why your asking this because the beginnig of this post states exactly when the issue happens. If using Zoo from Yootheme with SP PageBuilder, if you want to go into the zoo system to make changes you muist first dissable the system plugin for SPB. This is hardly an ideal scenario, simply because you both have the same call to "ApplicationHelper"
The simple and I thought very obvious answer was to find all instances where "ApplicationHelper" was referenced within the files, replace it with "ApplicationHelperspb" and then that one file needs renamed.
I used notepad++ to find and replace all instances where ApplicationHelper was used inside each of the coded pages, and then renamed the actual file. Zip it up, and install it.
I have had to do this countless times, in fact every time you provide an update I have to run it, and I now do it on a live site, so its perfectly stable.
If you do a clean install of any one of your templates. Update SPB to the latest build, then install Zoo into the system, and try to modify the zoo layouts, you will encounter the error. You dont reallly need my modified installable source, but if you want it you can download it from this link https://www.cksvcs.co.uk/testing/sppagebuilder.zip