Feed aggregator

Commit 415900 by arthuregg

Drupal CVS Log - Fri, 09/03/2010 - 11:36
Commit #415900 by arthurf at 16:36 Media Mover: /modules/media_mover/class_media_mover_configuration.php 1.1.2.48 @ DRUPAL-6--2
Media Mover: /modules/media_mover/class_media_mover_file.php 1.1.2.35 @ DRUPAL-6--2
Media Mover: /modules/media_mover/class_media_mover_step.php 1.1.2.27 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_api.install 1.1.2.16.2.5.2.25 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_api.module 1.1.2.110.2.47.2.73 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_ui/media_mover_ui.module 1.1.2.60 @ DRUPAL-6--2
Media Mover: /modules/media_mover/modules/mm_compress/mm_compress.module 1.1.2.5 @ DRUPAL-6--2
Media Mover: /modules/media_mover/modules/mm_dir/mm_dir.module 1.1.2.12 @ DRUPAL-6--2 This is a major commit which changes the structures of configurations/steps/files. On an API level this should not make a difference, however much of how data is getting loaded to configurations and files has changed. Some internal functions to configurations/steps/files are now private to try to keep the api as simple as possible. Additionally the majority of the data saving is now done with drupal_write_record() in preperation for D7. End to end testing has been done, but it is likely that there will be regression because of the scope of the changes

Converting PDF to SWF

Media Mover issues - Wed, 09/01/2010 - 09:20

I'm trying to automate PDF to SWF conversion using 'pdf2swf' and Media Mover custom commands.

Media Mover is suppose to start when uploading a PDF using a CCK field which is being detected, no problem.

Where it goes wrong is during the Media Mover process. I have set the parameters to
Output file: [nid].swf
Command: /usr/bin/pdf2swf -f -T 9 -t -G [data-harvest_file] -o [output_file]

Afterwards, it is supposed to be saved as a flash node.

The problem is no .swf-file is created. So I'm not sure if the harvested file get parsed correctly at all.

user warning: Table 'mysite.media_mover_config_list' doesn't exist

Media Mover issues - Wed, 08/25/2010 - 11:07

After submitting issue #[893164] for this same 2.x dev version, I tried to roll back to the 1.x dev version and further to the 1.0-beta7 version, but both rollbacks resulted in the user warning message mentioned in this post title. removing MM modules Updating database didn't help, deleting MM tables helped but reinstalling any version of MM results in the same user warning message:

user warning: Table 'mysite.media_mover_config_list' doesn't exist query: SELECT * FROM media_mover_config_list mmcl WHERE mmcl.status != 'disabled' in /public_html/sites/all/modules/media_mover/media_mover_api.module on line 1215.

And line 1215 in media_mover_api.module is:
$results = db_query("SELECT * FROM {media_mover_config_list} mmcl WHERE mmcl.status != 'disabled'");

Please check this out, I am now apparently in the situation that I cannot properly install ANY version of MM without this user warning.

Fatal error: Call to undefined function media_mover_api_extract_form_data()

Media Mover issues - Wed, 08/25/2010 - 10:08

Fatal error: Call to undefined function media_mover_api_extract_form_data() in /public_html/store/sites/all/modules/media_mover/modules/mm_mailhandler/mm_mailhandler.module on line 162

The error message above appears after submitting the Step 1: 'Harvest attachments from an email account'.
All MM 6.x-2.x-dev modules enabled on Drupal 6.19 <<<

Commit 411610 by arthuregg

Drupal CVS Log - Tue, 08/24/2010 - 16:06
Commit #411610 by arthurf at 21:06 Media Mover: /modules/media_mover/class_media_mover_configuration.php 1.1.2.47 @ DRUPAL-6--2
Media Mover: /modules/media_mover/class_media_mover_file.php 1.1.2.32 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_api.info 1.1.2.1.2.2.2.3 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_api.module 1.1.2.110.2.47.2.70 @ DRUPAL-6--2
Media Mover: /modules/media_mover/media_mover_ui/media_mover_ui.module 1.1.2.58 @ DRUPAL-6--2 This is a big checkin that is bound to break many things. It requires drupal_queue and does some substaintial reorganization of the flow of the module. There is a bunch more cleanup to do, but major movement on queueing deletion of files, added some caching functions for file loading in, etc.

Doxygen url broken

Media Mover issues - Tue, 08/24/2010 - 08:29

As the title implies; The url to the doxygen index shows a fresh drupal installation so maybe the db got emptied?

Commit 410760 by arthuregg

Drupal CVS Log - Sun, 08/22/2010 - 14:50
Commit #410760 by arthurf at 19:50 Media Mover: /modules/media_mover/media_mover_ui/media_mover_ui.module 1.1.2.57 @ DRUPAL-6--2 #876112 by arthurf: fixes display of configuration details

Commit 410758 by arthuregg

Drupal CVS Log - Sun, 08/22/2010 - 14:41
Commit #410758 by arthurf at 19:41 Media Mover: /modules/media_mover/modules/mm_ffmpeg/mm_ffmpeg.module 1.1.2.13 @ DRUPAL-6--2 #876734 by arthurf: fixes the file output extension

Commit 410752 by arthuregg

Drupal CVS Log - Sun, 08/22/2010 - 14:31

auto run and saving node -- causes wait time for user

Media Mover issues - Thu, 08/19/2010 - 16:22

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?

deleting a configuration results in white screen / undefined function

Media Mover issues - Tue, 08/17/2010 - 13:12

There is an extraneous/erroneous chunk of step removal code still in media_mover_configuration::remove(), attached patch removes it and makes a slight update to the delete message to include configuration name/description.

Syndicate content