This topic has 11 replies, 4 voices, and was last updated 3 years, 7 months ago ago by Olga Barlow
We just updated all our plugins and themes including XStore core, but when you go into page or post editor, and try to click ‘Backend Editor’ to use Visual Composer, it does nothing and only the HTML code is showing with the content editor in ‘Text’ mode. When I deactivate XStore Core plugin, all the functionality comes back.
We also noticed that the ‘Screen Options’ drop down feature in WordPress was also not working – selections were not being activated when checked. Disabling xstore core, making a screen options selection (Show Excerpt) then turning xstore core back on did get around that issue though.
Not sure what we can do to fix this conflict though, we have child theme enabled in case that is relevant.
** It also seems we cannot get into the Customizer area at all **
Xstore core is on version 3.2.5
Theme version: 7.2.5
Visual Composer: 6.6.0
Please note this is an adult website so may trigger access filters.
Hello,
Provide us with WP Dashboard and FTP access. We’ll check the issue and help you.
Regards
See attached private info
If you log in, try to access the theme customizer, or visual composer in a page or post you will see the issue. Note that if you deactivate xstore core the functionality resumes. Please note this is a live website.
HI
We have access your website dashboard and edit the page Visual Composer is working absolutely fine https://prnt.sc/106ekzf
Please check your website after removing cache or use a different browser if you still facing any issue let us know or send us highlighted screenshot where you are facing the issue.
I cleared Chrome cache and also opened in Edge but in both cases what happens is visual composer won’t activate in the page: https://prnt.sc/106izyu
Also, Customize does not load, it just get’s stuck like this: https://prnt.sc/106j0rj
This is not just on my laptop, but others too. Can’t understand how you got in to it. Can you try customizer too please.
There are loads of js errors showing in the console which shouldn’t be there – they point to a js issue: https://prnt.sc/106ix48
If I deactivate xstore core, these issues all go away
HI
Kindly click on Backend Editor Button it will display page editor in your website. https://prnt.sc/106sblv
You can see page builder is working fine in your website we are again send you highlighted screenshot https://prnt.sc/106sd9p
I have been trying to click the backend editor, when I do nothing happens it just stays stuck in HTML view and I cannot get into the theme customizer either. I have cleared my entire browser cache and it’s still the case, I do not understand how you are not getting the same error?
I even disabled all plugins and switched on only vsual composer and xstore core and it was still displaying this issue. So it’s definitely not anything else. What device/browser are you using, maybe there is something in that.
I’m not just being stupid here – there is definitely something wrong. We just cannot understand how you aren’t seeing it too.
Hello!
I am Muhammad and will be assisting you with the issue.
First I apologize for all the inconvenience.
I see the issue on your end in your provided screenshots. And I have also tried to replicate it on my end but it does not happen, please see the video I have made for you:
https://share.getcloudapp.com/4gu1N5YN
Our plugin Xstore core is compatible with bundled plugin wp-bakery.
Now I will explain what can be reasons for this issue.
-Very strong cache issue (sever cache+CDN)
-Browser-specific issue.
Can you please try on another browser or another device once to check if the issue appears there. If you see the issue on another device could you please share a video recording maybe we are missing any steps to replicate the issue?
I have checked your Home page, FAQ page, and some other pages. Can you please tell me if you see the issue on the specific pages?
Can you please share the URL of the pages?
And please clear out all your caches (Plugin+server+CDN) and try again.
Thank you!
**** Update – it’s working – it was CDN cache ***
thanks for all your help – it got us to the resolution we needed.
Hello,
You are welcome!
Regards
You must be logged in to reply to this topic.Log in/Sign up