Fatal Error after the Update

  • Resolved heikof

    (@heikof)


    1 month, 3 weeks ago

    Hello,
    I’m getting a critical error on a customer website after the update.

    What surprises me: Up until now, version 3.8.10 was running – the update is now on version 6.1.3. How does such a big jump in the version come about?

    The debugging log gives the following error:

    [31-Jan-2025 06:18:07 UTC] PHP Warning: require_once(/home/ch260107/web/…/wp-content/plugins/seo-booster/inc/CacheManager.php): Failed to open stream: No such file or directory in /home/ch260107/web/…/wp-content/plugins/seo-booster/seo-booster.php on line 110
    [31-Jan-2025 06:18:07 UTC] PHP Fatal error: Uncaught Error: Failed opening required ‘/home/ch260107/web/…/wp-content/plugins/seo-booster/inc/CacheManager.php’ (include_path=’.:/usr/share/php’) in /home/ch260107/web/…/wp-content/plugins/seo-booster/seo-booster.php:110
    Stack trace: 0 /home/ch260107/web/…/wp-settings.php(526): include_once() 1 /home/ch260107/web/…/wp-config.php(95): require_once(‘…’) 2 /home/ch260107/web/…/wp-load.php(50): require_once(‘…’) 3 /home/ch260107/web/…/wp-admin/admin.php(34): require_once(‘…’) 4 /home/ch260107/web/…/wp-admin/index.php(10): require_once(‘…’) 5 {main}

    thrown in /home/ch260107/web/…/wp-content/plugins/seo-booster/seo-booster.php on line 110

    Best regards
    Heiko

Viewing 1 replies (of 1 total)
  • Plugin Author Lars Koudal

    (@lkoudal)

    Dear Heiko,

    Thank you for bringing this to our attention, and we sincerely apologize for the inconvenience caused by the recent update.

    Regarding the Version Jump: The significant leap from version 3.8.10 to 6.1.3 is due to several intermediate versions that were developed but ultimately not released over the past years. These versions involved complete rewrites that were abandoned for various reasons. To maintain consistency and reflect the most current iteration of our plugin, we advanced the version number accordingly.

    About the error: We have identified the issue causing the critical error you’ve encountered. Our team has promptly addressed this, and we have just released a new update that resolves this fatal error.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.