Skip to content
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

Closed
kebbet opened this issue Jul 10, 2022 · 17 comments
Closed

1.13.2 breaks sites, fatal error #84

kebbet opened this issue Jul 10, 2022 · 17 comments
Milestone

Comments

@kebbet
Copy link
Contributor

kebbet commented Jul 10, 2022

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

@nerra0pos
Copy link

Same here.

@Clearified
Copy link

same here! I hope vendors will fix this asap

@Clearified
Copy link

Rolled back the old version until coders releases a fix. :)

@mattbedford
Copy link

Same here..... sigh.

@fischerpu
Copy link

Same here. Rolled back to previous version resolves the issue.

@ezkayaker
Copy link

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.

@Regnalf
Copy link

Regnalf commented Jul 10, 2022

A quick temporary fix for all who need a solution right now
https://wordpress.org/support/topic/a-fixed-zip-for-fatal-error-missed-vendor-folder/

@mahmoudgad94
Copy link

mahmoudgad94 commented Jul 10, 2022

Just fire inside the folder plugin (or fire it local and upload it to the server)

composer install --no-dev

@rleeson
Copy link

rleeson commented Jul 10, 2022

Just fire inside the folder plugin (or fire it local and upload it to the server)

composer install --no-dev

This or composer dump-autoload on the server if available or locally then upload are the best way to handle temporarily patching the issue until the team resolves the CI issue.

@rleeson
Copy link

rleeson commented Jul 10, 2022

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 vendor directory for some reason. Is there a separate build workflow for that which doesn't use the Github Workflow?

@dc0063
Copy link

dc0063 commented Jul 10, 2022

The error is from the following requirement at the beginning: require_once DIR . '/vendor/autoload.php';
as this references the plug-in folder of wp-crontrol as might be expected. However, the path is incorrect as the file is in the folder - wp-optimize, not wp-crontrol - ANOTHER PLUG-IN.
Ooops.
Disabled, waiting for the update

@sebastianhutter
Copy link

sebastianhutter commented Jul 10, 2022

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

@MichaIng
Copy link

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.

@dakman
Copy link

dakman commented Jul 10, 2022

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

@johnbillion
Copy link
Owner

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.

@johnbillion johnbillion added this to the 1.14.0 milestone Jul 10, 2022
@mjgardner
Copy link

A quick temporary fix for all who need a solution right now https://wordpress.org/support/topic/a-fixed-zip-for-fatal-error-missed-vendor-folder/

Page not found error on that link

@johnbillion
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests