Posted by mfb on June 5, 2009 at 7:14am
Jump to:
| Project: | Media Mover |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | reviewed & tested by the community |
Issue Summary
This is probably the wrong fix but there is some logic error preventing configurations from running during cron runs.
| Attachment | Size |
|---|---|
| media_mover-cron.patch | 856 bytes |
Comments
#1
btw the documentation for media_mover_api_run_control_extend() is kinda confusing. "Controls for throttle mechanisms. Returns true if the configuration should be running. If one module returns true, return true which stops the running of the configuration"
#2
Anyone else seeing this issue? Am I crazy?
#3
The patch did not solved problems with cron or saving to filefield on my end.
i have checked against #486206: Files transcoded but not added to filefiled and #368956: Error saving to filefield in cron, also did not help for #532170: MM is encoding a file any time i run config.
cheers !
#4
Even i am facing the same issue. Any updates ?
#5
I've hopefully fixed the logic in the run control function. Can somebody please review and let me know if it is now functional?
#6
I just tested newest dev version (2009-Sep-17) on fresh drupal install. the issue is solved, single config did its thing on cron run.
great, that is 3th issue solved today ;)