Critical error after setting separator

After saving the change, if you revisit the settings page, is the error still there? I assume you’re using Breadcrumb NavXT 7.0.2, is that correct? The issue itself isn’t due to setting the separator to “/” (I can’t reproduce it on my testbed by doing this), but I have a couple of ideas of what may be causing this. It seems to be a flavor of the post type added too late in init (in this case in 7.0.2 it didn’t get registered before the 9000 priority).

Hello John,

I got the same error too. And it also prevents me to change some settings because I can’t save them.

Best regards,

Igor

1 - Uncaught TypeError: Argument 1 passed to mtekk\adminKit\form::textbox() must implement interface mtekk\adminKit\setting\setting, null given, called in /home/example.com/wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php on line 429 and defined in /home/example.com/wp-content/plugins/breadcrumb-navxt/includes/adminKit/class-mtekk_adminkit_form.php:179
Stack trace:
#0 /home/example.com/wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php(429): mtekk\adminKit\form->textbox(NULL, '6', false, 'The template fo...')
#1 /home/example.com/wp-includes/class-wp-hook.php(303): bcn_admin->admin_page('')
#2 /home/example.com/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
#3 /home/example.com/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#4 /home/example.com/wp-admin/admin.php(259): do_action('settings_page_b...')
#5 /home/example.com/wp-admin/options-general - /home/example.com/wp-content/plugins/breadcrumb-navxt/includes/adminKit/class-mtekk_adminkit_form.php - 179

Hello John,

Yes, I am using 7.0.2 version. My PHP is 7.4.
The error is still there, if I revisit this page.

I disabled my plugin KingComposer for a moment and saving option came back. So it was the reason. Maybe you could take a look and see if they can be compatible? Thanks!

Hello

I have the same or similar error:

Fatal error: Uncaught TypeError: Argument 1 passed to mtekk\adminKit\form::textbox() must implement interface mtekk\adminKit\setting\setting, null given, called in /home/customer/www/localhost/public_html/wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php on line 539 and defined in /home/customer/www/localhost/public_html/wp-content/plugins/breadcrumb-navxt/includes/adminKit/class-mtekk_adminkit_form.php:179 Stack trace: #0 /home/customer/www/localhost/public_html/wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php(539): mtekk\adminKit\form->textbox(NULL, '6', false, 'Il modello per ...') #1 /home/customer/www/localhost/public_html/wp-includes/class-wp-hook.php(307): bcn_admin->admin_page('') #2 /home/customer/www/localhost/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array) #3 /home/customer/www/localhost/public_html/wp-includes/plugin.php(474): WP_Hook->do_action(Array) #4 /home/customer/www/localhost/public_html/wp-admin/admin.php(259): do_action('settings_pag in /home/customer/www/localhost/public_html/wp-content/plugins/breadcrumb-navxt/includes/adminKit/class-mtekk_adminkit_form.php on line 179

If I deactivate the Avada Builder plugin, the Save button reappears, otherwise I can’t do anything

How do we do it?

Update:
I provisionally solved this: I turn off the Avada Builder plugin, customize NavXT as I prefer, apply to the site, and then reactivate Avada Builder

• This reply was modified 3 years, 1 month ago by davidebrig.

@davidebrig So, my guess is that Avada is trying to have a private CPT so it registers it under the admin_init action so it only is available in the admin area (I’ve seen another plugin do this). CPTs are supposed to be registered in the init action (and is why you will get errors in the Breadcrumb NavXT settings page as it was registered after the 9000 runlevel of init). In the next release of Breadcrumb NavXT, the settings page will alert you to these misbehaving CPTs and custom taxonomies with a dismiss-able message (and will not try to generate settings for them which is what is causing the PHP errors).

@mtekk in my case while register_post_type
'public' => TRUE, was the trigger for the same error. Removed or set to FALSE did the trick

Edit: sorry, no, remove “public” just remains that my CPT is not editable by breadcrumb NavXT, but I can change the other settings in this plugin

• This reply was modified 3 years ago by jf9xcsdd.