Fatal error in customizer (Elementor)

Resolved

Hardline1988

(@hardline1988)

Hello guys, i am facing a fatal error in the customizer section of the dashboard.

This is the error:

Fatal error: Uncaught Exception: Supplied nav_menu_item value missing property: status
in /home/536745.cloudwaysapps.com/uhyybsmgud/public_html/wp-includes/customize/class-wp-customize-nav-menu-item-setting.php on line 183

Call stack:

WP_Customize_Nav_Menu_Item_Setting::__construct()
wp-includes/class-wp-customize-nav-menus.php:818
WP_Customize_Nav_Menus::customize_register()
wp-includes/class-wp-hook.php:307
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:331
WP_Hook::do_action()
wp-includes/plugin.php:476
do_action()
wp-includes/class-wp-customize-manager.php:933
WP_Customize_Manager::wp_loaded()
wp-includes/class-wp-hook.php:307
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:331
WP_Hook::do_action()
wp-includes/plugin.php:476
do_action()
wp-settings.php:620
require_once()
wp-config.php:78
require_once()
wp-load.php:50
require_once()
wp-blog-header.php:13
require()
index.php:17

Any clues how to fix this?
Thanks

Viewing 11 replies - 1 through 11 (of 11 total)

Cena (a11n)
(@cena)

2 years, 8 months ago

Hi @hardline1988 ,

I just tested by activating Elementor with the Storefront theme, and I don’t see an error:

![] (https://cloudup.com/cKl8wf_tBPV+)

I also tried with Elementor + Hello Elementor theme, also with no errors.

What theme are you using?

Where exactly do you see the error – in Appearance->Customize, or somewhere else?

Best,
Cena

Laurent OneChai
(@lolobu)

2 years, 7 months ago

This post might help : https://alex.blog/wordpress-plugins/add-descendants-as-submenu-items/comment-page-2/#comment-240480
I had the same issue and this patch fixed it.

Thread Starter Hardline1988
(@hardline1988)

2 years, 7 months ago

Thank you very much Laurent, now it works like a charm!

Plugin Support Stef (a11n)
(@erania-pinnera)

2 years, 7 months ago

Hey @hardline1988,

I am so glad that @lolobu was able to answer your questions correctly. Thanks, @lolobu! ⭐

I am going to mark this thread as solved. If you have any other questions, @hardline1988, please let us know.

Take care!

Laurent OneChai
(@lolobu)

2 years, 7 months ago

@erania-pinnera, wouldn’t it be possible de release a new version of the plugin with this patch so that it’s fixed for everybody without having to find the fix in the forum?

Cena (a11n)
(@cena)

2 years, 7 months ago

Hi @lolobu –

It would be helpful if we could get more information about when/how the error is affecting people.

As I mentioned earlier, I wasn’t able to duplicate the problem with Elementor, which is what the OP mentioned using.

That said, @hardline1988 didn’t answer my questions about the specific theme being used, or where exactly he’s seeing the error, so we don’t know anything other than some code from 2019 on a blog post seems to ‘fix’ the problem for you and he.

We don’t know what it’s fixing, or what’s going wrong, exactly, or where.

For example, for yourself, what happens if you only have the Add Descendants plugin installed, with a default theme? What happens as you add plugins, including Elementor – does it continue to work? Then try switching to a different theme – what happens then?

The point is, there could be a theme and/or plugin conflict as well, AND the cause could be different for each of you. We just don’t know at this point.

If you can tell me exactly how to duplicate this error with Add Descendants in the Customizer, along with the other plugins and theme you’re using, I will be more than happy to test it, and go from there.

Best,
Cena

Laurent OneChai
(@lolobu)

2 years, 7 months ago

Hi,

I don’t think that this error is theme related. I got the very same error while switching between 4 different themes (oceanwp, twentytwenty, twentytwentyone and twentytwentytwo).
I don’t use Elementor either. I disabling all my other plugins didn’t make any difference either.
And given the code added by the patch, the issue seems to be menu content related and nothing else.
But I didn’t dig further in trying to change my menu (and the menu items for which I checked the option to add descendants in the menu) to find the exact reason.

Cena (a11n)
(@cena)

2 years, 7 months ago

Hi @lolobu ,

Well, that’s frustrating!

You can report and/or request this here:

https://github.com/Automattic/add-descendants-as-submenu-items/issues

The only reason I’m not reporting it myself is that I can’t duplicate the issue yet.

I would like to try testing this more completely, though, if you’re willing. If so, please send me a Site Health report (showing your theme/plugins) so I can attempt to duplicate the problem. Send it via email to [email protected] and mention the URL of this thread – I’d love to track down where this issue is coming from!

Best,
Cena

Plugin Author Jake Morrison (a11n)
(@jakeom)

2 years, 6 months ago

I’ve applied a patch to fix this issue and released an update (1.2.2). Please let us know if you continue to have issues with customizer.

Cheers,

Jake M.

Thread Starter Hardline1988
(@hardline1988)

2 years, 6 months ago

The update seems to work just fine. Thank you Jake

Plugin Support Jay
(@bluejay77)

2 years, 6 months ago

@hardline1988,

Thanks for letting us know!

I’m marking this topic as resolved now, but if you have any further questions or need some more help, you’re welcome to reply here or open another thread.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Fatal error in customizer (Elementor)’ is closed to new replies.