Reviewed & tested by the community
Project:
Media Mover
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Jun 2009 at 07:14 UTC
Updated:
17 Sep 2009 at 03:13 UTC
This is probably the wrong fix but there is some logic error preventing configurations from running during cron runs.
| Comment | File | Size | Author |
|---|---|---|---|
| media_mover-cron.patch | 856 bytes | mfb |
Comments
Comment #1
mfbbtw 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"
Comment #2
mfbAnyone else seeing this issue? Am I crazy?
Comment #3
szczym commentedThe 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 !
Comment #4
venkiparam commentedEven i am facing the same issue. Any updates ?
Comment #5
arthurf commentedI've hopefully fixed the logic in the run control function. Can somebody please review and let me know if it is now functional?
Comment #6
szczym commentedI 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 ;)