Fatal Error on 1.13.x versions – only stable 1.12.1

+1 (.1.13.2)

Same problem here.

Warning: require_once(/wp-content/plugins/wp-crontrol/vendor/autoload.php): failed to open stream: No such file or directory in /wp-content/plugins/wp-crontrol/wp-crontrol.php on line 45

Fatal error: require_once(): Failed opening required '/wp-content/plugins/wp-crontrol/vendor/autoload.php' (include_path='.:/usr/share/php') in /wp-content/plugins/wp-crontrol/wp-crontrol.php on line 45

Please fix it.

Thank you

• This reply was modified 2 years, 4 months ago by shappix.

Almost two hours and still no fix.

You can disable the plugin until a fix is available by renaming the plugin folder to ‘wp-control1’ via FTP.

Remane the /wp-content/plugins/wp-crontrol to /wp-content/plugins/wp-control to disable the plugin temporary until the developers fix it.

• This reply was modified 2 years, 4 months ago by shappix.
• This reply was modified 2 years, 4 months ago by shappix.
• This reply was modified 2 years, 4 months ago by shappix.
• This reply was modified 2 years, 4 months ago by shappix.
• This reply was modified 2 years, 4 months ago by shappix.

yes Shappix,
actually renaming the folder from wp-cRontrol to wp-control in the plugins folder did the trick, the site is back online and the plugin works perfectly

Do they even test this stuff before they release it??

Apparently not

same here, I thought I was crazy but no, just a simple update made my site broken… sick!

Thats a dang shame! Crashed my site, and had to recovered from a backup. Thats when I figured it was this plugin. Good Bye WP-Crontrol. Guess I’ll check back in 2 months to see how this was handled by the author.

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

Thanks for the reports everyone.

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.