I’m using pagebuilder to add images and text to a web page. After adding approx 35 images and text I started getting this message every time I update the page:
“A script on this page may be busy or may have stopped responding. You can stop the script now, open in debugger or let the script contiune.”
Script: http://simplemindedsims.com/wp…wp-color-picker,editor&ver=4.3:4
What is it and how do I get rid of it?
Hi Littlelambsy
That script is actually something WordPress generates that includes all the core WordPress admin scripts – so it’s more than just the Color Picker. Because these are all core files, it’s hard for us to say why these scripts might have stopped responding.
A few questions to help me figure out the issue. Does it only happen after you add a certain number of widgets in Page Builder? What browser are you using? How many plugins are you using besides Page Builder?
Hello Greg, Thank you for responding so quickly. To answer your questions:
1. Yes it only happens after a certain point. I was adding images and text widgets and all was fine. Then when I got to about 35 (approx) I started getting this error message after I clicked “update”. When I get the message I always click “continue” and it seems fine. I clicked cancel at one point and it messed up the whole page. So now I just click continue. It works ok but it’s irritating to have it pop up whenever I update.
2. I’m using the latest version of FireFox
3. I’m using 22 plugins, including pagebuilder.
Note. My friend who is also signed into my account tried adding an image and updating but she never got the error message and she uses the same version of FireFox. She in Texas I’m in Canada – weird!
Hi Littlelambsy
Given the number of plugins you’re running and the delay you’ve described, this sounds like a resource limitation. Besides living with the delay other options would be trying to reduce the number of plugins you’re running OR in the medium term, moving to a hosting package with greater resources.
Hope that helps a little to explain what’s going on :)
Thanks for the reply. It seems the problem is gone. For some reason I’m not getting the error message anymore. Thanks for the suggestions. :)
Super, really glad to hear it.
All the best with your site :)