Weaver Xtreme 6.2 Problem reports

[TNGenWeb]

This reply has been marked as private.

[beethoven]

Thanks @weaver for the prompt answer. I’m not sure what you mean with no longer defined Menus. I didn’t change any menu on my site for a long time and all menus and submenus are working

Yes I’m interested to try  the edit you propose and I know ist only until the next wp release, hoping they issue will be fixed

[paviland]

Just to say all works well for me on all sites now with 6.2.1.  Many thanks for the hard work and swift turnaround

[hkp]

@Weaver
Looks great!
Just one small sore thumb for next time…..
Regards and thanks!

https://www.dropbox.com/s/qrejhu39nt66waf/HKP-Weaver-Options.jpg?dl=0

[GR8FL]

Why has this been updated from 6.2 to 6.2.0.1? Should I wait a bit more until it fleshes out?

There’s this too from WordFence (I hadn’t updated everything yet).

https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-themes/weaver-xtreme/weaver-xtreme-theme-507-authenticatedcontributor-stored-cross-site-scripting-via-display-name

[Weaver]

@GR8FL:

The WordFence post is correct.

Weaver Xtreme 6.2 (and later) correct the issue. Note the only issue they found was that a Contributor (or above) could add malicious code simply by editing their name. I would have thought that WordPress core would have prevented such an entry to begin with rather than relying on each and every Theme and plugin to validate the user name.

The 6.2.0.1 update corrects a styling error in the Desktop -> Dashboard -> Appearance -> Weaver Xtreme Admin page.

[Weaver]

@hkp –

Thanks for the catch. Will be fixed in next release. Was a stray file in the subthemes directory that was a save of a working version of the new Ahead subtheme, so should not hurt anything. (The default name of a saved settings file when the Plus plugin is installed.)

[Weaver]

@beethoven –

This is a bug fix for WordPress 6.2.

The problem is found around line 833 in WordPress core code in file /wp-admin/nav-menus.php.

          if ( function_exists( 'get_post_states' ) ) {
               $menu_post   = get_post( $menu_item->object_id );
                   /*
                    * Suggested fix for bad nav_menu_item post - likely caused by now missing parent
                    *  which can result in $menu_post being NULL at this point
                    *
                    */
                   if ($menu_post != NULL) {   //*** add a NULL check
                       $post_states = get_post_states($menu_post);
                       if ($post_states) {
                           $menu_item->type_label = wp_strip_all_tags(implode(', ', $post_states));
                       }
                   } // end of added NULL check
          }

This fix adds a check for an empty menu item.

The problem seem to be in an item found in a menu defined in one or more of the defined menus. It does not have to be in a menu you are actually using, but in one of the defined menu. And I’m not sure this is really the cause. The REAL cause could be deeper. And note that this is not Weaver Xtreme releated. Switch to any other theme that uses the Customizer, and those errors will show just the same as with Weaver Xtreme.

The only thing I discovered is that the SQL database had record of a menu item. Turns out Menu Items are saved in the list of posts. There are actually many types of posts beyond the expected ‘page’ and ‘post’. So there is a record in the ‘post’ list that is called a menu item that has bad data (most likely a missing id of the page of the menu item), it will create the error messages you listed. The code fix I proposed simply ignores such records.

[Weaver]

This reply has been marked as private.

[beethoven]

Thank you @weaver, but can you tell me where exactly I have to put the bug fixing lines ? It’s not clear to me

[scrambler]

@beethoven –

As he mentioned

“The problem is found around line 833 in WordPress core code in file /wp-admin/nav-menus.php.”

[Weaver]

@beethoven –

Sorry. It is around line 833 in WordPress core code in file /wp-admin/nav-menu.php  (nav-menu not nav-menus)

[travincult]

I just updated Weaver Xtreme. Unfortunately, this has caused a lot of issued on my site.

Literally all font (families) now have changed on my website https://travelinculture.com/ (this both applies to the menu and the text. I believe that no fonts look the way they should. Moreover, I used to have only sans serif fonts – now it seems that titles/headlines are serif (instead of Lato) when I style with CSS?!? In general I use Lato (for headlines), Open Sans for normal text and in a few cases Roboto. It is as if all my fonts are now being ignored.

Another issue is that in my posts there is suddenly a year (e.g. 2023) appearing – overwriting my text in the beginning of the post after the country field, see for example https://travelinculture.com/where-to-stay-in-tokyo/ (below the title, right after JAPAN)  or https://travelinculture.com/old-city-of-jerusalem-trip-history-western-wall-temple-mount/ (below the title, right after ISRAEL).

@weaver, I hope you can sort this out for me. Thank you.

[beethoven]

Thank you both @weaver and @scrambler. I saw “around line 833” but I’m not sure to understand “around” Where do I put the code ? before line 833 ?  I’m not a php specialist and would not do something wrong.

If that is the case, you may want to try and delete/redo the bad menu, or wait for a WP fix…

[TNGenWeb]

This reply has been marked as private.

[scrambler]

@TNGenWeb

I don’t see how the theme could change subtheme by itself…

Also updating to 6.2 should not change ANY settings

[Author]

Posts