Site logo

Archived topic

Sidebar Editing Msg: An error has occured.

13 replies · Started by Moses on July 14, 2021

Viewing posts 1–14 of 14

Thanks in advance for the support. When editing a side bar, I am faced with the following - An error has occurred. Please reload the page and try again. This happens when creating a new widget, or even trying to edit the existing default widget. Tried on several browsers, and even a different computer to eliminate the possibility of a system or browser issue. All plugins disabled except for GP Premium and Generate Blocks. Latest updates all applied.

Hi there,

Is this only happening in sidebar widgets or all widgets?

If it's all widgets, does the same issue happen if you activate a Twenty series WP theme?

It appears to be happening with all widgets - tried the header and footer as well, same issue. Also just tried it on a twenty series theme and it is also occurring on the other theme. How strange. :/

Yeah that means it's not a theme issue.

I did a quick Google search and looks like there are lots of reasons that might trigger this.

You could try checking with the WordPress support team or your hosting support to see if they can help identifying the issue.

Also, it seems to only happen from within the Customizer. When editing the widget text in WP's Appearance > Widget menu - it seems to save the changes.

Oh heck.

Yeah unfortunately I'm not able to replicate this on my end.

Re-installing WordPress is also an option to make sure that no files are corrupted.

Thanks for your help. This is a fresh install as it is. I'll see what I can find.

All the best.

Sounds good.

Let me know if you find anything - I'd like to know as well :)

Edit

Oh wait... I was wrong - That was not it. It's Generate Blocks. 100% Generate Blocks. When I deactivate Generate Blocks it works fine. It's not even a function of a conflicting Element, I disabled the one page hero I had made in GB, and still the issue persisted.

Thank you!

I was able to replicate this now. Will log it as a bug and get it fixed in the next version :)

Awesome! Thanks!

This archived topic is closed to new replies.