Fatal error on settings page after updating from 6.6.0 to 7.0.2

  • Hi!

    After updating the plugin from 6.6.0 to 7.0.2 and running the migration, I can’t save the settings anymore because the page isn’t loadling completely. The Save button and the WP admin footer is missing. This is the Query Monitor output:

    Fatal error: Uncaught Error: Argument 1 passed to mtekk\adminKit\form::textbox() must implement interface mtekk\adminKit\setting\setting, null given, called in /.../wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php on line 539
in /.../wp-content/plugins/breadcrumb-navxt/includes/adminKit/class-mtekk_adminkit_form.php on line 179

Call stack:

    mtekk\a\form::textbox()
    wp-content/plugins/breadcrumb-navxt/class.bcn_admin.php:539
    bcn_admin::admin_page()
    wp-includes/class-wp-hook.php:303
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:327
    WP_Hook::do_action()
    wp-includes/plugin.php:470
    do_action()
    wp-admin/admin.php:259
    require_once()
    wp-admin/options-general.php:10

    Additionally, at the top of the page the following notice is displayed:

    Found 50 unknown legacy settings: bpost_dlm_download_taxonomy_referer, Hpost_dlm_download_template, Hpost_dlm_download_template_no_anchor, apost_dlm_download_root, bpost_dlm_download_hierarchy_display, bpost_dlm_download_archive_display, Spost_dlm_download_hierarchy_type, bpost_dlm_download_hierarchy_parent_first, bpost_dlm_download_version_taxonomy_referer, Hpost_dlm_download_version_template, Hpost_dlm_download_version_template_no_anchor, apost_dlm_download_version_root, bpost_dlm_download_version_hierarchy_display, bpost_dlm_download_version_archive_display, Spost_dlm_download_version_hierarchy_type, bpost_dlm_download_version_hierarchy_parent_first, Htax_dlm_download_category_template, Htax_dlm_download_category_template_no_anchor, Htax_dlm_download_tag_template, Htax_dlm_download_tag_template_no_anchor, bpost_iwp-log_taxonomy_referer, Hpost_iwp-log_template, Hpost_iwp-log_template_no_anchor, apost_iwp-log_root, bpost_iwp-log_hierarchy_display, bpost_iwp-log_archive_display, Spost_iwp-log_hierarchy_type, bpost_iwp-log_hierarchy_parent_first, bpost_amn_smtp_taxonomy_referer, Hpost_amn_smtp_template, Hpost_amn_smtp_template_no_anchor, apost_amn_smtp_root, bpost_amn_smtp_hierarchy_display, bpost_amn_smtp_archive_display, Spost_amn_smtp_hierarchy_type, bpost_amn_smtp_hierarchy_parent_first, bpost_dd_layouts_taxonomy_referer, Hpost_dd_layouts_template, Hpost_dd_layouts_template_no_anchor, bpost_dd_layouts_archive_display, apost_dd_layouts_root, bpost_dd_layouts_hierarchy_display, Spost_dd_layouts_hierarchy_type, bpost_widget-area_taxonomy_referer, Hpost_widget-area_template, Hpost_widget-area_template_no_anchor, bpost_widget-area_archive_display, apost_widget-area_root, bpost_widget-area_hierarchy_display, Spost_widget-area_hierarchy_type

    Best regards
    Matthias

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Havlik

    (@mtekk)

    Based on the specific setting that caused the issue, it appears you have taxonomies that are getting added after the priority level of 8999 on the init action. By default hooks into the init action are at priority 10, and Breadcrumb NavXT runs at 9000, which should be much later than anything else. It is highly suggested that whatever adds the taxonomy so late is changed to add it earlier (smaller priority number, my guess is someone used priority 9999, which for adding CPTs or taxonomies makes it difficult to play nice with other plugins/code).

    Thread Starter Matthias Pabst

    (@matthiaspabst)

    Hi John,

    I found it. The plugin FV Flowplayer Video Player breaks the Breadcrumb NavXT settings page. You only need to activate the video plugin – then visit the settings page “/wp-admin/options-general.php?page=breadcrumb-navxt”. You should see a fatal error in the categories area.

    Is this a problem with your plugin or with the Flowplayer plugin?

    Best regards
    Matthias

    Plugin Author John Havlik

    (@mtekk)

    Thanks for digging into this to identify the plugin that caused the problem. I took a look at said plugin, and it looks like that plugin is registering the fv_player_encoding_category taxonomy at the incorrect time. It registers this taxonomy in the create_encoding_categories function that hooks into the admin_init action. The problem with this is not only is this after all of the init filters, but it makes the taxonomy unavailable outside the dashboard/admin area (which may be the intent, but if that is the intent, the taxonomy should be registered as a private taxonomy as well, which it currently is not).

    I’m adding a check/message in the next version of Breadcrumb NavXT that lets the user know in the settings page if a CPT or taxonomy was detected to be registered too late (a dismiss-able message as in some cases, such as with FV Flowplayer it seems to be intentional) and to not include settings form elements for said CPTs and taxonomies (aims to prevent PHP error messages).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error on settings page after updating from 6.6.0 to 7.0.2’ is closed to new replies.