Fatal error: 1.13.2

  • ResolvedModerator Steven Stern (sterndata)

    (@sterndata)


    Volunteer Forum Moderator

    2 years, 8 months ago

    Two of my sites went down after updating to 1.13.2. It looks like a file may be missing?

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

    It appears the “vendor” directory is missing:

    -rw-r--r-- 1 bertha-www bertha-www  2269 Jul 10 07:56 composer.json
drwxr-xr-x 2 bertha-www bertha-www  4096 Jul 10 07:56 css
drwxr-xr-x 2 bertha-www bertha-www  4096 Jul 10 07:56 js
-rw-r--r-- 1 bertha-www bertha-www 18014 Jul 10 07:56 LICENSE
-rw-r--r-- 1 bertha-www bertha-www 16805 Jul 10 07:56 readme.md
drwxr-xr-x 2 bertha-www bertha-www  4096 Jul 10 07:56 src
-rw-r--r-- 1 bertha-www bertha-www 71388 Jul 10 07:56 wp-crontrol.php
[sdstern@sugaree wp-crontrol]$ pwd
/var/www/bertha.sterndata.com/wordpress/wp-content/plugins/wp-crontrol

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

  • Same

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 45 of the file /home/user/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php. Error message: require_once(): Failed opening required ‘/home/user/public_html/wp-content/plugins/wp-crontrol/vendor/autoload.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’)

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

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report.

    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.remarpro.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.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error: 1.13.2’ is closed to new replies.