Bug in LayTheme 11.5.1 – Right-click in Gridder causes React render error
-
Hi everyone, hey @arminunruh
after updating LayTheme from 11.4.9 to 11.5.1, I encountered a reproducible issue in the gridder editor. Whenever I right-click on any element inside the gridder, the context menu does not open and the following error appears:
Gridder render error:
Minified React error #185After opening the browser console, I also received:
Maximum update depth exceeded.
This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate.
React limits the number of nested updates to prevent infinite loops.I already cleared browser cache, disabled all custom JavaScript and plugins but the problem remained in all cases. I downgraded LayTheme back to 11.4.9, and the issue disappeared immediately. Right-clicking in the gridder works normally again.
Has anyone else experienced this issue, or is this a known regression in 11.5.1? I'd be happy to provide any additional information or help with testing if needed!
-
hey i cant replicate this.
Can you send your wp-admin login to info@laytheme.com and send a link to this topic? Then I will check out why this happens on your site directly. -
Hey! Thanks for looking into this – just sent you the info.
-
-
Hmm, the login info didn't work. Can you send it again?
-
ok! i will release an update now and then you can try if that fixed it please
-
Problem solved. Thanks for looking into this!
-
@spontans It works fine now for me after the latest update. But I had to clear the cache first to make it work. Give it a try!
-
@spontans It works fine now for me after the latest update. But I had to clear the cache first to make it work. Give it a try!
@chris.vuko Thanks Chris, I will try now
-
Hey @chris.vuko, hey @arminunruh, hey @spontans, I have the same problem. I've cleared all the caches, but I still keep getting this message: “Gridder render error: Maximum call stack size exceeded” whenever I try to add an image. Do you have any ideas?
-
can u send a screenshot of the error, so i can see the line in the javascript where it happens, cause it didnt happen for me when i tested on my browsers
u can try a different browser too
-
-
ahh! ok im happy it works now
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login