Fatal Error on 1.13.x versions – only stable 1.12.1

  • Resolved raffi007

    (@raffi007)


    2 years, 11 months ago

    The Recent 1.13.x versions all crash the website
    I have downgraded to the 1.12.1 and the site is back online

    Please fix this error ASAP

    Thank you

Viewing 12 replies - 1 through 12 (of 12 total)
  • NAROLLES

    (@narolles)

    2 years, 11 months ago

    +1 (.1.13.2)

    shappix

    (@shappix)

    2 years, 11 months ago

    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, 11 months ago by shappix.
    terrapop

    (@terrapop)

    2 years, 11 months ago

    Almost two hours and still no fix.

    Ross

    (@rmdglasgow)

    2 years, 11 months ago

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

    shappix

    (@shappix)

    2 years, 11 months ago

    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, 11 months ago by shappix.
    • This reply was modified 2 years, 11 months ago by shappix.
    • This reply was modified 2 years, 11 months ago by shappix.
    • This reply was modified 2 years, 11 months ago by shappix.
    • This reply was modified 2 years, 11 months ago by shappix.
    Thread Starter raffi007

    (@raffi007)

    2 years, 11 months ago

    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

    dlmcycling

    (@dlmcycling)

    2 years, 11 months ago

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

    Thread Starter raffi007

    (@raffi007)

    2 years, 11 months ago

    Apparently not

    wparold

    (@wparold)

    2 years, 11 months ago

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

    ashes00

    (@ashes00)

    2 years, 11 months ago

    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.

    icedterminal

    (@icedterminal)

    2 years, 11 months ago

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

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    2 years, 11 months ago

    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.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fatal Error on 1.13.x versions – only stable 1.12.1’ is closed to new replies.