Hello!

First, thank you very much for your job!!!

Here is a story. I recently settled BM to upload all backups to Amazon S3 (downloaded php class and place it in BM folder, everything works great). But then I updated my website from Drupal 6 to Drupal 7. As a result, the folder of BackupMigrate was changed. And then, yep, I forgot I have to re-download PHP class and to place it in module's folder again... So, I was without any backups for a month and I discovered a problem only when my website was broken :(

Now I resrote everything, but I am worrying, what if BM would get some updates in the future? What if I will move my website to another webhost? etc etc

So, it would be great, if amazon S3's php class could be stored at sites/all/libraries and NOT at module's own folder. It would be much more safe for update and web site development.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ronan’s picture

Status: Active » Closed (works as designed)

Go a head and move it to 'sites/all/libraries/s3-php5-curl/' It'll still work.

R

Geldora’s picture

Thanks :)

But you should change a description. BM clearly states where should I place PHP class (/includes folder inside the module). Please, add the line "move it to 'sites/all/libraries/s3-php5-curl/' It'll still work."

:)

squarecandy’s picture

Title: Please, allow to store Amazon S3 PHP Class at sites/all/libraries/ for Amazon S3 support. » Better document Amazon S3 PHP Class at sites/all/libraries/ for Amazon S3 support.
Version: 7.x-2.4 » 7.x-3.x-dev
Component: Code » Documentation
Issue summary: View changes
Status: Closed (works as designed) » Needs review
FileSize
2.1 KB

Great to know this works. Obviously putting this file inside the module directory will get overwritten by updates. I put some clarifying text in the readme and the onscreen error message.

dddbbb’s picture

Status: Needs review » Needs work

Agreed that this change is needed. I was surprised that a module of this prestige was recommending that I add a library to the module directory. In fact, I don't think there's any benefit to indicating that that would also work; just advise people on how to add it to the libraries directory and avoid anything other than best practice.

couturier’s picture

Status: Needs work » Postponed (maintainer needs more info)

Can anyone verify if this issue is still a concern with the newest 7.x-3.2 release?

couturier’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Closing after more than two weeks with no activity.