latest update locked up in “saving” mode in Gutenberg

Hi Sharon,

Unfortunately, I can’t seem to replicate this. 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.

I don’t think I need to do anything further with Bundle. After Site Origin Bundle was updated, the problem immediately occurred. When I deactivated the bundle, the problem with saving mode being locked up disappeared. I am not using any SiteOrgin themes. The theme I use is from Kadence Themes, Ascend theme. And everything functions fine.

I did continue testing by reactivate the bundle and somehow it worked right this time. However, the Page Builder was not activated. I activated the PBuilder and the problem came back. It saved the change but the “saving mode” was still running. I refreshed, and the saving mode was working right. I tested the PBuilder twice by activating, deactivating, and activating again, and the problem was there both times when the PB was activated. Hope I make sense here. I currently have PB deactivated and everything is working right. And I clear the cache also.

• This reply was modified 5 years, 10 months ago by sharon135.

Hi Sharon

Thanks for the update.

We’re, unfortunately, unable to replicate this issue locally. A plugin conflict test will allow you to see if a working baseline is available. It just takes a moment, temporarily deactivate all plugins in one go except for Page Builder and the Widgets Bundle then test the issue. If the issue remains, we can rule out a plugin conflict, if the issue is resolved, we know to start looking at a possible plugin conflict.

In the absence of a distinct error, this is the quickest method of investigation.

Hi, Sharon,

The fix for me was installing Black Studio TinyMCE Widget version 2.6.6. I can’t find the changelog now that I have installed it, but it references resolved conflicts with SiteOrigin’s Page Builder. [Prob coincidentally, I’m also using Ascend Premium.]

All fixed — hope this helps someone else!

Thanks for the update ??

Here is the issue report: https://github.com/black-studio/black-studio-tinymce-widget/issues/45. Black Studio 2.6.6 resolves.