At the moment, media_mover_api_queue_file_process_worker is attempting to run a configuration off of the file object, which doesn't seem to contain the necessary configuration data, included patch offers one possible solution by loading the configuration. This also removes the $file->step_order++, as this was causing problems with the step order in the latest version. May have been unnecessary in the first place due to http://drupal.org/node/915230

CommentFileSizeAuthor
#1 file_worker_load_config.patch937 bytescivicpixel

Comments

civicpixel’s picture

civicpixel commented
StatusFileSize
new file_worker_load_config.patch937 bytes

forgot to attach the patch.

civicpixel’s picture

civicpixel commented
Status: Active » Needs review
arthurf’s picture

arthurf commented

It is likely that in one of the previous refactors steps were not getting stored correctly on files - this might have been the reason for this queue worker not working, but otherwise, I'm fine to switch over to your patch- it's essentially the same thing.

darrick’s picture

darrick commented

The configuration data was being passed in okay. However, process_next was calling the wrong step. AFAICT the step_order should not be advanced before calling run. This was causing every other step to be skipped.

Commit is here: http://drupalcode.org/project/media_mover.git/commit/a97ba79