Also I would like to notice that this happen when there are widgets in mega menu widgets
Hi zaur,
Sorry to hear you’re having problems with the update. I suspect you have a widget added to the menu which is not agreeing with MMM, which you have added to the menu on your live site but not on localhost (which is why you don’t see the error on localhost).
I am not sure what would cause that in 2.3.2, as I don’t recall making any changes to the code in that area, so I’m not sure if reverting back to 2.3.1 will help, but it is worth trying quickly:
Please could you:
Install the “WP Rollback” plugin
Roll back Max Mega Menu to v2.3.1 (it’s safe to go back through versions)
In the screenshot, please can you also scroll to the right a bit and let me know which line number the error is occurring on?
Regards,
Tom
Please also let me know if this is happening with all widgets, or just one in particular (if it’s just one of them, please let me know the name of it), and see if you can replicate the same issue locally using the same widget. Please also check if you have any plugins which might modify the behavior of widgets (e.g. Widget Logic) – basically anything you can do to help me replicate the same problem here would be a big help 🙂
Regards,
Tom
Hi Tom, it was just text & custom menu widgets. For this website I disabled MMM menu. But you should fix that issue, because I’m sure it would happen again with someone
-
This reply was modified 9 years, 5 months ago by
zaur1979.
Hi Zaur,
I agree 🙂
Many (most) users are using Custom Menu or Text Widgets within their mega menus (including me on megamenu.com), so I think the problem must have been with your specific setup, it hasn’t been reported before.
I suspect it was due to either a conflicting plugin or a problem with a shortcode you had added into the text widget content. It’s impossible to say exactly what it was without me being able to either debug the issue as it’s happening, or replicate it here.
If you do come across the error again, please let me know which line number it is on. That would be a huge help, and I may be able to work around the error without needing to replicate it exactly here.
Regards,
Tom
Hi Tom, it is me again. Today I faced this issue twice in our customer’s website (we use this menu in our theme). It is solved only after I removed widgets from max mega menu widget area and added again.
Hi Zaur,
Sorry to hear it’s happened again.
It’s been 5 months since you first posted, and this hasn’t been reported by anyone else in the mean time.
In my last response I asked if you could note down the line number of the error (it’s just missing from your screenshot). Did you note that down?
Regards,
Tom
