My site also went down with a fatal error after I tried to update to the latest version of WP Crontrol.
Same, can’t access my site via either the front or the WP back-end.
-
This reply was modified 3 years, 11 months ago by
kazerniel.
All,
Please refer to this post for the root cause and the temporary fix.
Cheerios!
@ generosus: Many thanks. That fixed it!
-
This reply was modified 3 years, 11 months ago by
richards1052.
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 ww.wp.xz.cn 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.
@ John: Thanks for the update.
Another thing to remember after deleting the updated version with the error, is that when you install the Github version you should clear your browser cache before activating the plugin. When I tried to activate before clearing the cache I got an error msg saying “file not found.” CLearing the cache got everything working again.
I had the same issue reported this afternoon.
Since I had received an email notice of the plugin update earlier today I suspected it might be the source of the issue.
Sure enough.
Much to my pleasant surprise, when I got back into the system I noticed that a plugin update was available and the comment associated with the update referenced the issue.
Well done!!!
Errors happen but its a pleasure to deal with a developer that is willing the admit the issue and provide a fix as quickly.
Great plugin & developer.
Thanks for what you do (for us).
Does anyone know whether John fixed the issue that broke sites in the new update. Or is this a rollback to the version before the update which broke our sites?
Thank you for 1.14.0!
: )
