Version 1.2.5 Causing Fatal Error After Update

  • Resolved IndeMoJo

    (@butisitart)


    9 months ago

    I updated Advanced Tabs Gutenberg Block from 1.2.4 to 1.2.5. As soon as it was reactivated, WordPress threw a fatal error.

    WordPress version 6.8.2
    Active theme: Neve FSE Child (version )
    Current plugin: Advanced Tabs Gutenberg Block (version 1.2.5)
    PHP version 8.4.11

    Error Details
    =============
    An error of type E_ERROR was caused in line 55 of the file /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php. Error message: Uncaught Error: Failed opening required ‘/home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/includes/loader.php’ (include_path=’.:/opt/alt/php84/usr/share/pear:/opt/alt/php84/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php:55
    Stack trace:
    #0 /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php(36): ATBS_BLOCKS->includes()
    #1 /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php(64): ATBS_BLOCKS->__construct()
    #2 /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php(77): ATBS_BLOCKS::init()
    #3 /home/gojocom/public_html/wp-content/plugins/advanced-tabs-block/plugin.php(81): atbs_block_init()
    #4 /home/gojocom/public_html/wp-settings.php(545): include_once(‘/home/gojocom/p…’)
    #5 /home/gojocom/public_html/wp-config.php(104): require_once(‘/home/gojocom/p…’)
    #6 /home/gojocom/public_html/wp-load.php(50): require_once(‘/home/gojocom/p…’)
    #7 /home/gojocom/public_html/wp-admin/admin.php(35): require_once(‘/home/gojocom/p…’)
    #8 /home/gojocom/public_html/wp-admin/plugin-install.php(16): require_once(‘/home/gojocom/p…’)
    #9 {main}
     thrown

    I reverted back to v 1.2.4 and it works fine.

    Hope this is an easy fix for you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hervé Suaudeau

    (@suaudeau)

    8 months, 4 weeks ago

    Same error for me.

    Matija

    (@matija80)

    8 months, 4 weeks ago

    Same issue here.

    timholden

    (@timholden)

    8 months, 4 weeks ago

    A file name has the wrong case.

    wp-content/plugins/advanced-tabs-block/includes/Loader.php should be a lowercase “l” not uppercase “L”. Rename it and it will work. Bit sloppy and took me an hour to find as I could not get logging working properly on the website I had it installed on.

    Thread Starter IndeMoJo

    (@butisitart)

    8 months, 4 weeks ago

    When I checked the case of the PHP file, mine did have a lowercase L: loader.php. What I ended up trying was changing it to an uppercase L, refreshing my FTP client, going back into WordPress, admin page and refreshing. I still got the fatal error

    Went back to the FTP client change capital L back to a lowercase L and refreshed the FTP client. Went back to the WordPress, plug-ins admin, page, refreshed, and that fixed it.

    What I don’t understand is why if the file originally had a lowercase L why didn’t it work? And why did changing to uppercase L. refreshing, then changing to a lowercase L & refreshing fix the issue.

    Very odd … but at least now it’s working. Thank you.

    timholden

    (@timholden)

    8 months, 4 weeks ago

    I have had issues with FTP clients not refreshing when the server file changed case – particularly if they are windows clients which tend to be a bit hit and miss as to whether they think about case as all.

    Thread Starter IndeMoJo

    (@butisitart)

    8 months, 4 weeks ago

    Mac client here:Transmit. Just figured I’d let you know. It’s all good now and working. Thanks again.

    tonydjukic

    (@tonydjukic)

    8 months, 1 week ago

    How is this “Resolved” if it requires manually editing the plugin?

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

The topic ‘Version 1.2.5 Causing Fatal Error After Update’ is closed to new replies.