Fatal error when upgrading to 1.16.1

  • Resolved rambo3000

    (@rambo3000)


    3 years ago

    Hi,

    Got this when upgrading plugin:

    PHP Fatal error: Uncaught Error: Class ‘ActionScheduler_Lock’ not found in /var/www/html/wp-content/plugins/popup-maker/packages/action-scheduler/classes/abstracts/ActionScheduler.php:29\nStack trace:\n#0 /var/www/html/wp-content/plugins/popup-maker/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(103): ActionScheduler::lock()\n#1 /var/www/html/wp-includes/class-wp-hook.php(292): ActionScheduler_QueueRunner->maybe_dispatch_async_request(”)\n#2 /var/www/html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)\n#3 /var/www/html/wp-includes/plugin.php(484): WP_Hook->do_action(Array)\n#4 /var/www/html/wp-includes/load.php(1072): do_action(‘shutdown’)\n#5 [internal function]: shutdown_action_hook()\n#6 {main}\n thrown in /var/www/html/wp-content/plugins/popup-maker/packages/action-scheduler/classes/abstracts/ActionScheduler.php on line 29, referer: https://xxx.com/wp-admin/update-core.php?action=do-plugin-upgrade

Viewing 4 replies - 1 through 4 (of 4 total)
  • Maria T

    (@mariatogonon)

    3 years ago

    Hello @rambo3000 – sorry to hear that you are having these errors.

    The ActionScheduler_Lock error must be related to some type of caching, object caching or PHP opcache etc. Those files were included with the previous version of PM but never used so we removed them. Only an opcache could hypothetically still run code from those files that didn’t exist, so clearing it should be the fix.

    Could you please try to clear it again form your end? Additionally, do you know of some server-side cache that you might have from your web hosting company? If you are using any CDN/Cloudflare to your site then could you please temporarily disable the cache of Cloudflare or switch it off temporarily and check it again to see if the error still persists?
    ​
    ​You can also reach out to your hosting provider – they should be able to assist you with this. 

    I hope that helps.

    Ashish

    (@ashishpatel1992)

    3 years ago

    I also go this error while updating. Although it was non-blocking one so didn’t mess up anything.

    Maria T

    (@mariatogonon)

    3 years ago

    Hi @ashishpatel1992 – we are sorry to hear that.

    Is everything works properly on your end now? Otherwise, could you please try the suggestions above to see if the error still persists?

    Hope that helps.

    Thread Starter rambo3000

    (@rambo3000)

    2 years, 12 months ago

    So far it looks like it throws error only once during upgrade. Popups seems to be working though.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error when upgrading to 1.16.1’ is closed to new replies.