How To Fix The Call To Undefined Method ApplicationHelper::getName() From The Conflict Of Your Product And Yootheme Zoo And WidgetKit.
Keith S
Installing SP Page Builder 5 Pro (5.2.6) causes a conflict error with the ApplicationHelper that Yootheme Zoo and Widgetkit use.
I have found that to gain access to the configuration section or to upgrade/install Zoo, you have first to disable your plugin "System - SP Pagebuilder," or you will get the error "Call to undefined method ApplicationHelper::getName()."
For WidgeKit, you are not able to access the application information needed when using Zoo as the source because of the above conflict.
I like what has been done with Pagebuilder 5, and I would like a fix to be applied so I can still use your product.
I have found posts on Yootheme that have identified that the new code in your product is causing problems. A few temporary workarounds have been shared, but ultimately, they do not fix the issue, and taking a site down to disable your product to access theirs can not be the final answer. I'm unsure if you can work together and come up with a solution or update your new code implementation to avoid conflict with others.
Ofi Khan
Accepted AnswerHello Keith S
Please share a screenshot of your issue to understand it better. Take a screenshot and share via any platform. For example: Lightshot or Imgur.
Also share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.
Best regards
Keith S
Accepted AnswerHello Ofi Khan,
Sorry for the delay. I have shared with you the credentials and a video to help explain what I have observed. Attached is the image of the error.
Ofi Khan
Accepted AnswerPlease contact 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.
Keith S
Accepted AnswerHello Ofi Khan,
This is what I received from Yootheme support on this issue:
** 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.
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. 😉
Thank you**
Do you know if there has been any progress on implementing a fix? Is there a way that the two development teams can come up with a working solution?
Ofi Khan
Accepted AnswerI am not sure about it. We cannot change in our code only to support other extensions. We also have some limitations or liability to check. We cannot change in the core code on a sudden. I definitely understand your situation from an user point of view. Maybe we will think about it if we get a huge volume of requests about it.
Ofi Khan
Accepted AnswerSorry, there is no temporary fix available for this issue. It requires the code change in the core files. For now, you can do this. When working with ZOO, disable SP Page Builder system plugin and vice versa. I have added high priority for this feature. Hopefully, the development team will review it and will act soon.
craig kennedy
Accepted AnswerThis is a real issue yes. I too have this problem. Luckily when I have created the pages using SP page builder, I no longer require the SP Page builder system to be enabled, while I do need to enable the Zoo system ap, so for you guys, the easy way to fix this for use is create the various pages in SP that you need, its likely these wont actually change, however the zoo side there are constant changes being made, so when the SP is done, turn of the SP page builder system plugin, page builder continues to work on the front end and you can edit the zoo app in the backend.
Its definetly not ideal but I plan on looking at both alternatives to SP page builder and Zoo to find something that can work together.
Clockworx Solutions
Accepted AnswerHas this issue been resolved? We are experiencing the same issue.
Ofi Khan
Accepted AnswerHello Clockworx Solutions,
Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing. Rest assured, I will look into this issue for you and work to resolve it as quickly as possible.
Please post a new question regarding your issue. We will check and help you.
Best regards
Benedikt Vitt
Accepted AnswerWe have the same Issue when Alphaindex is enabled in Zoo, not only in the administrator. So disable the Plugin shortly is no Option. The Problem is that the Pagebuilder uses BuilderAutoload::loadHelperClasses(); On one side, yours or Yootheme, is some work to do and it would be great if one of you using namespaces
Thanks forward