I updated a wordpress on its new version with all the plugins installed including toolset.
Everything works except toolset. When I create a product here is the error that is displayed in red and in the console (attachment) JS errors. I am in version php 7.4, but all the rest of the plugins are installed on the last versions ( attachment 2 - plugin list on the website )
Hello. Thank you for contacting the Toolset support.
That is really strange.
In order to check there is no conflict between the third-party plugin or theme:
Could you please try to resolve your issue by deactivating all third-party plugins as well as the default theme to check for any possible conflicts with any of the plugins or themes?
- Do you see any difference?
The reason for the issue is mentioned with the above errata page, can you please get in touch with WPBakery page builder plugin support and check with them if they can help you in this regard.
Hi Minesh,
I'm sorry, but i purchased a wp-backery license to get in touch with wpbackery contact and this ti the reply of my demand : This will require further debugging to identify the exact code causing the conflict on your setup.
Once found, a custom js code can be written to handle the same.
If you are looking for such debugging and customisation to fix a third party conflict, then we can recommend checking our customisation partners: WPKraken and Codeable who can debug and fix the same.
i'm very disapointed. It's not my fault and i don't want to buy another tech to solve this issue. I have replied to them, I will keep you posted on their response.
Hi Minesh, i receive the reply of support WPbackery :
"Hi,
The WPBakery Page Builder plugin on your setup, works fine if the toolset plugins are disabled.
If the issue was specific to WPBakery Page Builder then it would have persisted even with toolset disabled and WPBakery Page Builder enabled. However, the issue disappears when toolset plugin is disabled on your setup.
The issue specifically in this case is due to the conflict between the two and it will require further debugging into toolset plugin to identify the exact code which causing it. Unfortunately debugging a third party plugin is beyond the support reach and hence in previous reply we had recommended customisation partners who can debug it's code to check it further.
Thanks,"
So, what can we do now ? because i'm block and my customer is not very happy.