And now after making some other changes S3 has disappeared from the Destinations column when looking at the list of jobs.
from a different post…
file with error: class-cron.php on line 140 & 141
$temp_fodler = scandir( BackWPup::get_plugin_data( 'TEMP' ) );
foreach ( $temp_fodler as $temp_file ) {
$temp_fodler should be $temp_folder
fix that and S3 will show up.
Also you need at least php5.2.6
Thanks so much, @mrkingid. That tip worked! That enabled the S3 option to appear on the first tab.
I did run into a bunch of other errors with S3, such as, despite “US – Standard” being selected:
Fatal error: Uncaught exception ‘Guzzle\Service\Exception\ValidationException’ with message ‘Validation errors: [LocationConstraint] must be one of “EU” or “eu-west-1” or “us-west-1” or “us-west-2” or “ap-southeast-1” or “ap-northeast-1” or “sa-east-1″‘ in /home/cybnet/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Command/AbstractCommand.php:376 Stack trace: #0 /home/cybnet/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Command/AbstractCommand.php(272): Guzzle\Service\Command\AbstractCommand->validate() #1 /home/cybnet/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Client.php(223): Guzzle\Service\Command\AbstractCommand->prepare() #2 /home/cybnet/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Command/AbstractCommand.php(162): Guzzle\Service\Client->execute(Object(Guzzle\Service\Command\OperationCommand)) #3 /home/cybnet/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Command/AbstractCommand.php(213): Guzzle\Servic in /home/xxxxx/public_html/about/wp-content/plugins/backwpup/sdk/Aws/Guzzle/Service/Command/AbstractCommand.php on line 376
Lots of errors still. Am running a backup now, and will see how that goes.
I fixed those lines, but still don’t see S3 anywhere. The server I’m on is running PHP version 5.2.17, so I should be good there. Any other ideas?
Actually, when I looked at backwpup.php, I saw this line:
if ( function_exists( 'curl_exec' ) && version_compare( '5.3.3', PHP_VERSION, '<=' ) && class_exists( 'BackWPup_Destination_S3' ) )
So it looks like in order to continue to use S3, you have to be at version 5.3.3 or higher. Am I reading that correctly?
Looks like that’s it; just looked up the Amazon S3 php sdk that this plugin includes and found this mentioned in the Readme:
Minimum requirements
PHP 5.3.3+ compiled with the cURL extension
A recent version of cURL 7.16.2+ compiled with OpenSSL and zlib
@matt: Yes it is correct. The most new SDK all developt with PHP 5.3+.
@mrkingid: i have found the bug and fix it.
@cyberetto: the problem is only on buckt creation in US Standart. I think it is a problem of the sdk. Create the buckt with the AWS S3 Console will work https://console.aws.amazon.com/s3 with the plugin too.
Whua, whau wait a minute.
My S3 has completely disappeared, too. Not cool, Daniel.
So, in order to get it back I need to upgrade all of my hosted domains using BWPU to PHP 5.3.3 all of a sudden?
And that without warning and a bit of an advanced heads-up?
Oh, boy — this has bitten me, too. I feel very unhappy.
Anonymous User 7658014
(@anonymized_7658014)
@nadworks You can also grab an older version from here until you’re ready to move to PHP 5.3.3: http://wordpress.org/extend/plugins/backwpup/developers/
Granted, a bigger warning than the one in Description (pulled from the readme file) would have been appropriate, but then again: don’t you guys never click the Details link next to the upgrade message?
