Support

We ran across an interesting issue when performing the following:

1) Configure a backup to upload to Amazon S3 (new or legacy version) and use the [SITENAME] parameter in the path (not the bucket).
2) Run the backup from within wordpress and it will upload to the correct location (bucket/[SITENAME]/).
3) Setup a cron job to run (such as "/usr/bin/php5-cli /public_html/wp-content/plugins/akeebabackupwp/app/cli/backup.php --profile=2") and it will upload to a different path, substituting "akeeba-backup" in place of the [SITENAME] parameter (bucket/akeeba-backup/).

Using the [SITENAME] variable was useful for us since we can import an akeeba backup profile and not have to change that particular setting. Is that something that is not supported in the Wordpress version of the plugin?

I attached a log of the cli backup as well as a backup run from the back end.

Thank you!

If I understand you correctly, the easiest way to do that would be to set up a separate profile using akeeba-backup as the path instead of [SITENAME] and call the new profile from the CRON job.

We were actually just testing the cron job to setup a daily backup, and ran it from both the backend and the command line and were surprised to find it uploading to two different locations.

We'd like the cron job execution of the backup profile and the wordpress backend execution of the backup to both go to the same location, and it's been our experience that with the Joomla version of the component that is what happens when the [SITENAME] variable is used in the path. So if the name of the site is "website" and the upload path in Amazon S3 is /daily-backup/[SITENAME]/[DATE]/, it would upload to /daily-backup/website/2014121914/backup.jpa

This is what it does when run through the back end of Wordpress, but the same profile run through the command line or cron job uploads to /daily-backup/akeeba-backup/2014121914/backup.jpa, which wasn't the expected behavior.

It looks like it's using the plugin name or something besides the website name in place of [SITENAME] when the backup job is run from the command line, as opposed to the actual website name when run from the backend.

This can be very easily fixed by writing the website name in the path in the backup profile, but it wasn't the behavior we were expecting to see when using the [SITENAME] variable. At least it didn't replicate the behavior from the Joomla component.

Thanks!

My apologies, I did not properly understand your question. You are correct, that is not the expected behavior. I'll flag this for Nicholas' attention, but it is pretty late in his corner of the world, I doubt that he will be back today.

Hi Nicholas,

Thank you for the quick reply. Using the [HOST] variable sounds like a good solution: we'll go ahead and make that change. Thanks!