Weaver Xtreme 6.2 Problem reports

[Weaver]

The latest version of Weaver Xtreme is 6.2.1.x, so I’ve closed this topic for the pervious 6.2.0 version.

Most major problems seem to have been fixed, so I’m resetting this to just a sticky post for a bit, and then will just make it a normal post.

 

This thread is reserved for Weaver Xtreme 6.2 problem reports. This thread is intended for New issues found only in the new 6.2 version. Other questions about how to do something, or help with styling should be in their own new threads.

As usual with problems, please describe as completely as possible, and include a link to the site. If you don’t want others to view your site yet, you can mark your reply here as Private, and only you and the Moderators will see your post.

 

[hkp]

Works 100% as far as I have seen.

A couple of minor code-typos on the Options Page as per image:

https://www.dropbox.com/s/tt2v6n8wyyluidx/Weaver-V-6-2-graphics.jpg?dl=0

Regards and thanks!

[paviland]

This reply has been marked as private.

[GR8FL]

This isn’t a problem, but curious where the new option to add a “Menu Only Header” is located?

Thanks

[Weaver]

This reply has been marked as private.

[Weaver]

@GR8FL – Re: Menu Only Header

Not in Legacy interface…

Customizer -> WHAT interface -> Visibility -> Header

Customizer -> WHERE -> Header

[GR8FL]

Thanks @weaver

[Weaver]

This reply has been marked as private.

[hkp]

This reply has been marked as private.

[Weaver]

This reply has been marked as private.

[Weaver]

This reply has been marked as private.

[Weaver]

This reply has been marked as private.

[hkp]

This reply has been marked as private.

[Weaver]

@hkp – It was actually a bug in full theme 6.2… New one about to be posted.

[beethoven]

I don’t know if it is a 6.2 problem but today, if I open the customiser, I get this lines before the customiser , which I didn’t open for some time

<b>Warning</b>: Attempt to read property “post_status” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2288</b>
<b>Warning</b>: Attempt to read property “post_status” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2292</b>
<b>Warning</b>: Attempt to read property “post_status” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2298</b>
<b>Warning</b>: Attempt to read property “post_status” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2302</b>
<b>Warning</b>: Attempt to read property “ID” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2306</b>
<b>Warning</b>: Attempt to read property “post_status” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2310</b>
<b>Warning</b>: Attempt to read property “ID” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2315</b>
<b>Warning</b>: Attempt to read property “ID” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2319</b>
<b>Warning</b>: Attempt to read property “ID” on null in <b>/datas/yulpa171786/sites/fncta-midipy.fr/wp-admin/includes/template.php</b> on line <b>2324</b>
Moderators note: edited to remove redundant info.

[Weaver]

@beethoven – That error is coming from WP core. I actually encountered what I think is the same bug last week, and filed a bug report to WP.

If it is the same issue, it seems most probable that it caused by broken Menu definitions. I found it only happened from the Customizer, so it does seem like the same issue.

So I think what happens is that there is a Menu defined where one or more of the menu items are no longer defined – like a deleted post or page.

To find the problem, I actually had to edit the database directly to delete the offending menu item. I think I also could have edit my menu definitions. As you might imagine, I have a whole bunch of Menus defined for different testing scenarios.

If you are interested, I can provide a fairly simple edit for /includes/template.php that should work – but only until the next WP release, which may have been fixed by then.

[Author]

Posts