Pluggin broken since 5.2

  • Resolved willowleaf

    (@willowleaf)


    5 years, 10 months ago

    Today i had the time to update my website to WP 5.2. Since then my Breadcrumb NavXT gives my website a fatal error. I had to disable the addon via Recovery mode to run my website again. 

    This plugin failed to load properly and is paused during recovery mode.

An error of type E_ERROR was caused in line 247 of the file /home/www/www.achtmaalserallyclub.nl/www/wp-content/plugins/breadcrumb-navxt/includes/class.mtekk_adminkit.php. Error message: Uncaught Error: [] operator not supported for strings in /home/www/www.achtmaalserallyclub.nl/www/wp-content/plugins/breadcrumb-navxt/includes/class.mtekk_adminkit.php:247 Stack trace: #0 /home/www/www.achtmaalserallyclub.nl/www/wp-includes/class-wp-hook.php(288): mtekk_adminKit->filter_plugin_actions('<', 'breadcrumb-navx...') #1 /home/www/www.achtmaalserallyclub.nl/www/wp-includes/plugin.php(208): WP_Hook->apply_filters('<', Array) #2 /home/www/www.achtmaalserallyclub.nl/www/wp-admin/includes/class-wp-plugins-list-table.php(741): apply_filters('plugin_action_l...', Array, 'breadcrumb-navx...', Array, 'all') #3 /home/www/www.achtmaalserallyclub.nl/www/wp-admin/includes/class-wp-plugins-list-table.php(574): WP_Plugins_List_Table->single_row(Array) #4 /home/www/www.achtmaalserallyclub.nl/www/wp-admin/includes/class-wp-list-table.php(1244): WP_Plugins_List_Table->display_rows() #5 /home/www/www.achtmaalserallyclub.nl/www/wp-admin/includes/class-wp-list-table.php(1175): WP_List_Table->display_rows_or_placeholder

    I didn’t touch any code. I tried to delete and reinstall, but the fatal error stays.

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

  • These might relate also with too old PHP-versions.

    Thread Starter willowleaf

    (@willowleaf)

    The php on my server should be op PHP 7.3. I asked my hosting company.

    Plugin Author John Havlik

    (@mtekk)

    If you are getting an error in that part of the code, then you have another plugin or other code that is improperly messing with the links/actions array for the plugin_action_links filter (or a broken WordPress install). See the WordPress documentation for information on this filter: https://developer.www.ads-software.com/reference/hooks/plugin_action_links/

    It appears someone else had this problem recently as well. I’ll have to dig up what the ultimate cause was for them. I can confirm this is not a PHP5.3 issue or a WordPress 5.2 issue as I’m running both on my testbed without seeing this issue.

    • This reply was modified 5 years, 10 months ago by John Havlik.
    • This reply was modified 5 years, 10 months ago by John Havlik.
    Thread Starter willowleaf

    (@willowleaf)

    For now i have the pluggin disabled, but i love it. So i’dd rather have it back. I hope we can find what i can do to fix it.

    Plugin Author John Havlik

    (@mtekk)

    You’re going to have to do a little debugging (e.g. try disabling all other plugins and then try re-activating Breadcrumb NavXT). This does not appear to be an issue with Breadcrumb NavXT itself but rather something other code is doing to it.

    Plugin Author John Havlik

    (@mtekk)

    Just following up on this. After looking into this more, I am nearly certain it is not a Breadcrumb NavXT or WordPress 5.2 issue.

    The first parameter for the plugin_action_links filter has to be an array. If it is not, the plugins page is going to look goofy (the action links will be missing). You either have another plugin/other code that is behaving poorly, or a corrupt WordPress install. I strongly suggest disabling all plugins other than Breadcrumb NavXT to see if the problem persists (then re-enable the other plugins, one-by-one until the problem returns to identify the offending plugin).

    As an FYI, someone else reported this earlier in March (before WP 5.2 was released) see https://github.com/mtekk/Breadcrumb-NavXT/issues/218 Hence, I’m fairly confident this is not a WordPress 5.2 related issue.

    anonymized-15960438

    (@anonymized-15960438)

    We have such errors (no errors after disabling NavXT):

    WARNING: ILLEGAL OFFSET TYPE IN /WP-CONTENT/PLUGINS/BREADCRUMB-NAVXT/CLASS.BCN_BREADCRUMB_TRAIL.PHP ON LINE 848

    Warning: substr() expects parameter 1 to be string, array given in /wp-content/themes/pearl/partials/global/breadcrumbs.php on line 8

    Warning: Illegal offset type in isset or empty in /wp-includes/taxonomy.php on line 290

    Plugin Author John Havlik

    (@mtekk)

    @pqinstitute: Do you have more information regarding the page you visited that exhibited this issue? I’m not seeing this issue on my testbed and would like more information to hopefully reproduce it locally.

    anonymized-15960438

    (@anonymized-15960438)

    How can we send you this information?

    Plugin Author John Havlik

    (@mtekk)

    If there are details you can share in this thread, I’d prefer that. However, if there are details that can’t be shared in this thread, you can send me an email (via the email address in the plugin source code).

    Thanks a lot for your help @mtekk !
    Problem solved here. I confirm it was due to another plugin ??

    I had the error message mentioned above, which didn’t affect the way breadcrumbs were displayed on my site, but caused the WP dashboard not to display “All” and “Active” plugins lists (same problem as the user here: https://github.com/mtekk/Breadcrumb-NavXT/issues/218)

    Deactivating/Activating other plugins one per one permitted to solve both issues (error message + missing lists): the problematic plugin was “WP Editor”: a plugin not updated since a very long time.

    • This reply was modified 5 years, 9 months ago by Motionous.
    Thread Starter willowleaf

    (@willowleaf)

    Thank you @motionous
    I been in hospital and kept the breadcrumb pluggin off because i had no chance to take a better look. Disabling WP Editor did it for me too!

    • This reply was modified 5 years, 9 months ago by willowleaf.
    Plugin Author John Havlik

    (@mtekk)

    @motionous Thanks for taking the time to report back your findings!

    @willowleaf Thanks for reporting that the findings by @motionous applied to your situation as well.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Pluggin broken since 5.2’ is closed to new replies.