Can't find S3 drivers

I had the same problem and have located the problem. First off the readme instructions are a little vague. You are suppose to copy the drivers folder over as well. So that it will look like this:

modules/media_mover/drivers/Storage3

However, that is not the major issue. The drivers folder distributed does not contain all files needed to use them. They are PEAR packages and all the dependencies are not there, namely the PEAR base. Also if pear is not in your include path the paths of the requires in the distributed packages are incorrect. They rely on the pear base directory being in the include path. On top of this, if pear is in your include path then the files will look for and include the packages in your pear directory and not the packages distributed for media mover. I would say that the packages we meant to be optional but the mm_s3.module actually looks for the Storage3.php file that gives the driver not found error.

So to correct it make sure your directory structure matches the above path. And make sure you have pear and the appropriate pear packages installed and its path in your include path.

This is obviously not elegant in any way and I would think that this was not the intended way of doing it. It seems more as the developer had the above set when testing and so did not get these errors. I would like to hear from the developers what the actual intended way of using these libraries is? Use pear's packages? or do you intend to distribute your own?

To use S3, I relied on work that others had done. This intern relied on pear libraries. Since not everybody has them installed, I made a set of files that people can use. Probably, the S3 code should be rewritten so these aren't required so that it's easier for people to install. I'd gladly accept patches that do this.

As I am going to be using media mover with amazon web services, I have taken the task of rewriting this and more.

As a preview to what I have done:

1. Written a request module that is much more robust than drupal_http_request() and is has some better features for large files than the pear module does, such as streaming and expect 100.
2. In the process of writing a Amazon Web Services module that abstracts the services to drupal function calls. S3, EC2, and SQS will be in version 1. Many of the other services such as Turk, FPS, and others are planned for version 2.
3. Will be rewriting the Media Mover S3 module using the above modules to provide a more features while removing the dependency on the pear libraries.
4. Will be writing a EC2 and/or SQS module(s) for media mover. Not sure yet how I will integrate SQS into media move, whether it will be totally separate or just a feature that can be used if available.

I am writing this to show my intention to complete this. If anyone has any early comments send them my way. I will be creating separate issue tasks for each module I will be providing for media mover to collaborate on them once I have the base modules uploaded to d.o.

I'm very excited that you're interested in taking this on. I'd really like to see may of the things that media mover is doing abstracted- the s3 stuff is case in point. Let me know if you need support on this- I'd really like to see this happen.

a.

Please see:

http://drupal.org/project/aws