Support » Plugin: WP Crontrol » Version 1.13.2 stops WP login-page from being accessed

  • Resolved thedrumdoctor

    (@thedrumdoctor)


    I confirm with other users, this update renders the WordPress back-end login page inaccessible. Some sort of bug no doubt. I renamed the wp-crontrol folder and the login page functions again.

Viewing 14 replies - 1 through 14 (of 14 total)
  • This issue is that the newly introduced (in v1.13.0) wp-crontrol/vendor/autoload.php file is tried to be loaded but missing, the whole vendor directory.

    Confusing is that the last two patch versions (1.13.1 and 1.13.2) were already about fixing missing files, obviously not this one, while it is so fundamentally crashing the plugin right when activating it.

    Thread Starter thedrumdoctor

    (@thedrumdoctor)

    Maybe I’ll try and find the last known working 1.12 version and install that whilst waiting for a fix.

    Here is a fix 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.

    • This reply was modified 2 months, 3 weeks ago by Micha.
    • This reply was modified 2 months, 3 weeks ago by Micha.

    You only need to upload the vendor folder.

    Crashed multiple sites as described….renaming the plugin directory through ftp has the sites back up.

    Installing this version crashed my club’s site. I had to roll it back.

    I am running the latest WP and PHP.

    Thanks

    Disabled the plugin via WordPress recovery mode and all is working now. Watching this thread hoping to know when a fix is released. Thanks!

    Same here. I got the error white page message, “There has been a critical error on this website. Learn more about troubleshooting WordPress.”

    I had to login via FTP and disable the plugin by renaming the /wp-control plugin to /wp-control-temp to be get my site back.

    That’s the same error that I received. (“There has been a critical error on this website. Learn more about troubleshooting WordPress.”)

    Thank you

    All,

    Please refer to this post for the root cause and the temporary fix.

    Cheerios!

    I had rolled back to 1.12.1

    I think that I’ll wait until the author fixes the issue(s) and install the next version. It’s not a critical plugin for us at this point.

    Thank you

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    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 wordpress.org 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.

    Thanks @johnbillion !!!

Viewing 14 replies - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.