Jump to:
| Project: | Media Mover |
| Version: | 6.x-1.0-beta7 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I have a media mover configuration that copies a file to Amazon S3.
I turn on auto-run so when the node is created the file is then immediately copied to Amazon S3.
This works fine if the files are small and I don't notice too much of delay.
If I choose to use a large video file, once I click on Save to save the new node with the large video file. It continues to process (spin) while Media Mover is transferring the file to S3. The drupal website finally comes back when the transfer is complete.
I would much prefer that on save, the drupal save completes for the node and then triggers media mover configuration to run behind the scenes.
I did find a patch for the auto-run that increases the weight from 0 - 1 in the system table. I added that patch and ran update. But this has no effect.
Thoughts?
Comments
#1
patch applied: MM Auto Run needs higher weight so it runs after other modules which process file uploads that didn't help.
#2
Just don't use the auto run module. Media Mover will run from cron automatically. Feel free to reopen the issue if this doesn't answer your question.