fatal error

  • Resolved cekay

    (@cekay)


    2 years, 4 months ago

    updating the plugin caused fatal error at my site, I use server cron and wpengine host

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

  • I am experiencing this too. Updated the plugin on multiple sites and all were bricked. I checked the debug log on one site and figured out it was this plugin that caused it. Remove the plugin from all sites and they all started working again.

    Getting the following error in debug log:

    [10-Jul-2022 12:18:05 UTC] PHP Warning:  require_once(/sitefolder/public/app/plugins/wp-crontrol/vendor/autoload.php): failed to open stream: No such file or directory in /sitefolder/public/app/plugins/wp-crontrol/wp-crontrol.php on line 45
[10-Jul-2022 12:18:05 UTC] PHP Fatal error:  require_once(): Failed opening required '/sitefolder/public/app/plugins/wp-crontrol/vendor/autoload.php' (include_path='.:/usr/share/php') in /sitefolder/public/app/plugins/wp-crontrol/wp-crontrol.php on line 45

    https://github.com/johnbillion/wp-crontrol/issues/84#issuecomment-1179784419

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report.

    I’ve released version 1.14 which reverts the changes made in 1.13. The issue is not with the plugin itself but with its deployment process to www.ads-software.com which misses the files in the vendor directory. I’m investigating the root cause and hopefully I’ll be able to re-release the new update again soon.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘fatal error’ is closed to new replies.