-
Notifications
You must be signed in to change notification settings - Fork 391
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
's3-uploads' is not a registered wp command. #657
Comments
are you using bedrock? The vendor directory structure is different than this code expects. I was able to get around my constant server error with this quick and dirty change on a fork nickdnickd@26ef9f6 I am also seeing the CLI issue too though. For background I am running in a container. I can list the plugins, even re-activate the s3-uploads plugin, but I get the same error as your issue title. |
@etraininteractive I was facing the same error few days ago . The way I figure it out was to activate the plugin ( |
I got error:
find wp-cli.yml and add the code below
after I run
|
when I try to use 'wp s3-uploads verify' command to verify my configuration of the plugin, it throws an error saying, "'s3-uploads' is not a registered wp command."
I tried to resole by using this code in s3-uploads in php:
if ( ! class_exists( '\Aws\S3\S3Client' ) ) {
// Require AWS Autoloader file.
require_once dirname( DIR ) . '/vendor/autoload.php';
}
then, it throws CONSTANT error, even though I have added all the credentials like bucket name, bucket key and bucket secret in .env file.
Please help me to resolve this error.
The text was updated successfully, but these errors were encountered: