Even after deactivating all other plugins and clearing cache.
This is the error that comes up.
Can anyone advise? Thank you!
Cannot access Customize in Mono/North theme.
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi, thanks for posting :)
A plugin conflict test is a good place to start troubleshooting the problem. Please, find the details of the test below.
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Hi Andrew, thank you for responding!
I’ve tried disabling the plugins and clearing my caches multiple times (I made sure to read this forum before posting) and that didn’t work. I just tried switching over to a WordPress theme and that still didn’t help. Is this maybe something I should try contacting WordPress about?
Apologies, you did let us know that, thanks for your understanding. I read your thread, remembered the screenshot and forgot you let us know the steps already taken.
Ideally, we need to try and enable debug and debug logging. If you’re up for a little adventure, here is how that’s done. You don’t need to use FTP, you can also use your Hosting File Manager. If you’re able to set up debugging, please, let us know how it goes.
Thank you for all your help! I ultimately decided to contact WordPress directly. Support figured it out; they said the problem was a connection between my site and WordPress.com using the Jetpack and they’ve fixed the issue. Just an FYI for anyone else having this error!
Super, really glad to hear you made progress. Thanks for the update :)