When 'Store: save to a node', 'Save the file to' doesn't save?

What is the name of the action that you're using?

Note in the new dev release, the option for the cck field is saved so my main issue here i think is resolved...
I am not sure if it works, I will test that later...

The red form error still pops up though...
I just Add Step and next page doesn't have any of the config options as the video shows (just option to set Step Name)...
I then Save, and come back, and there is an error on page:
"warning: Invalid argument supplied for foreach() in /home/mysite/mysite.us/includes/form.inc on line 1434.". Not sure where this is right now, but something to look out for.

The 'Store: save to a node' action, is the step that brings the invalid foreach error.
I think everytime I was messing with this action, is where Ive gotten the foreach error. Disabling mm_node i think makes it go away, so somewhere in there maybe needs to get looked at... I can step through it later this weekend maybe.

Yes, all the steps are in the swf movie I captured as well if you want to see me adding the step and then attached error ...

Here is a screenshot... Note after Clicking Add Next Step.... the 'Save to Node' Step doesn't have any fields to fill other than step name... but when you save and come back all the fields are there (different behavior than other mm sub-modules?. not sure if its on purpose or not)... Anyway you come back and the error is there. Note: I have enabled languages on my site and none show up in the 'Save node in language:' dropdown. Who knows, maybe that is causing the error.

I just committed a fix for adding a new step to an existing configuration. This is a partial fix of "#8.

Cool, i reinstalled module. and Noticed
* You can pick the cck fields easier (doesn't show every possibility like before).

* The 'Store: back to a CCK field' step errors, pic attached... Maybe it needs to follow same format as 'Select from CCK' step: aka...

$form['mm_node_content_field_store_config']['cck_field_save_node'] = array(
...
'#options' => mm_node_cck_fields(array('text', 'filefield', 'imagefield')),
);
//Not sure if thats correct but Added that just so I can select something

* also the Select Step can choose Multiple cck fields (multiple select field), but you can only store back on 1 (single drop down select field). Not sure if thats standard (but Im only interesting in selecting and storing to 1 field).

* Ran my config attached and got this error:
"Fatal error: Cannot use string offset as an array in sites/all/modules/filefield/filefield.module on line 351"

So FFMPEG converts the file, so maybe messes up in Step 3?, last 2 issues might be resolved by adding:
$form['mm_node_content_field_store_config']['cck_field_save_node'] = array(
.....
'#multiple' => TRUE,

However it still doesn't save the converted file in the node. :(

Yes this is intentional- you can only attach a file to one cck field. I guess it could be the case that somebody who wants this but I'm going to say no or no

If thats the case, should the 'Select: from a CCK field' not be a #multiple select (just a single like the 'Store back to CCK' step).

can you either provide diffs or at least file names and line numbers?

Yep, I can do that.

I'll retest new release now.

EDIT:
So It looks like my config got done without error and associated the node with media mover file, but didn't actually save it in the cck field.
I'll take a double look at it tomorrow.
I think it may have tried to... The config errored until I changed the content type's cck field to accept .flv files.

EDIT#2: Think its working :). I just didnt select 'Replace existing file'. I'll see if I can get my slightly more complex configuration working.