-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.13.2 breaks sites, fatal error #84
Comments
Same here. |
same here! I hope vendors will fix this asap |
Rolled back the old version until coders releases a fix. :) |
Same here..... sigh. |
Same here. Rolled back to previous version resolves the issue. |
Yes. I have renamed the plugin folder wp-crontrol to wp-crontrol.bak. The plugin just took my site down on update to new version. |
A quick temporary fix for all who need a solution right now |
Just fire inside the folder plugin (or fire it local and upload it to the server)
|
This or |
It looks like the tagged release on this repository is correct and you can also download and install that directly. The ZIP downloaded from the WP plugins directory is missing the |
The error is from the following requirement at the beginning: require_once DIR . '/vendor/autoload.php'; |
We faced the same issue with my Wordpress installation. I was able to fix the Wordpress installation by manually re-uploadeding the current release 1.13.2 via sftp The zip provided by the Wordpress Plugins page is still missing the vendor folder |
Here is a fix to run from console until a new version has been released: cd /tmp
curl -LO https://github.com/johnbillion/wp-crontrol/archive/refs/tags/1.13.2.tar.gz
tar xf 1.13.2.tar.gz
mv wp-crontrol-1.13.2/vendor /var/www/wordpress/wp-content/plugins/wp-crontrol/
rm -R 1.13.2.tar.gz wp-crontrol-1.13.2 Adjust the path to your Wordpress accordingly, of course. |
yep effected us too... sucks cause it isnt recoverable.. eg takes the entire wp instance down and wp-auto updates probably wouldnt run since its a fatal error |
Thanks for the reports everyone. This is an unexpected bug in the GitHub action that I use to package the plugin for the wordpress.org plugin directory. I'm looking into options to fix it. |
Page not found error on that link |
I've released version 1.14 which reverts the changes made in 1.13 ("Unlucky for some"). I'll investigate the issue with the wordpress.org deployment, I can't immediately see why the vendor directory is missing because it's been accounted for in the build process. |
Admin notice says:
Warning: require_once(/home/user/sites/**/public_html/wp-content/plugins/wp-crontrol/vendor/autoload.php): failed to open stream: No such file or directory in /home/user/sites/**/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php on line 45
Fatal error: require_once(): Failed opening required '/home/user/sites/**/public_html/wp-content/plugins/wp-crontrol/vendor/autoload.php' (include_path='.:/opt/alt/php74/usr/share/pear') in /home/user/sites/**/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php on line 45
The text was updated successfully, but these errors were encountered: