Weaver-Extreme conflicts with WordPress 6.2: errors related to items-wrap

[parrot720n]

My wordpress website keeps going down with error pointing to “items_wrap’ ‘div class=”weaver-menu-clear”

I was instructed to get correction from Weaver Xtreme but I cannot find any instructions on making that correction.

http://www.westpalmbeachrental.condos

 

[parrot720n]

My wordpress website keeps going down with error pointing to “items_wrap’ ‘

I was instructed to get correction from Weaver Xtreme but I cannot find any instructions on making that correction.

[scrambler]

You need to give us more details about when and where you get that message.

But you can start by deactivating all non weaver plugins and see if that makes a difference

 

[Weaver]

Did you recently (like just before before the crash) change any menu items?

From looking at where your site is crashing, I would suspect faulty menu definitions. There is in fact a bug in WP 6.2 that can cause a crash if a menu item has become undefined.

To really see what is happening, you should edit your wp-config.php file in the root directory of the web site (using your host’s tools that let you edit files) and change the WP_DEBUG line to true:

define( ‘WP_DEBUG’, true );

That should make your site generate a useful message about the exact line where the site crashes.

 

Or provide the exact line that was pointing to someting. Need the full info which should include php function names and line numbers.

[parrot720n]

The problem was initially noted in https://myd2.net and the problem was identified at the line as shown on (see image)

I did change the wp-config.php as you directed.

I hope this is the information you needed.

[Weaver]

I am nearly 100% certain that this is an instance of a WordPress core bug.

The issue is that there is something wrong with your menu definition. It seems that either the definition has gotten corrupted, or more likely that some item in that menu no longer exists.

I first encountered the problem several weeks ago, and have reported the issue to WP, right down to the exact line of WP code. Another Weaver user also encountered the bug, and after completely re-defining the menu (make a new version), all worked again.

So the solution is to rebuild your menu.

I’m surprised that WP has not yet fixed the problem as it must be common as I now know of three cases of this just from Weaver Xtreme users.

I don’t remember for sure, but the problem might only show while in the Customizer, but I might be mixing that up with a different problem.

[beethoven]

I’m the one who had the problem and solved it by rebuilding the menu. In my case, the problem showed  only in the customizer.

[parrot720n]

Thank you very much… for some reason, the site is presently working and no error is showing. I will make the change on the menu if it recurs. Again, thank you so much.

[Author]

Posts