Image nodes don't work with actions module unpublish node action

Yes it does. i'm thinking i jumped the gun and it's a problem with the image module, not img_assist.
I haven't had much chance to look into it further.

No line number yet, but here are more details on what's happening:
When creating a new image node, the following error is displayed:
The selected file
could not be copied, because no file by that name exists. Please check that you supplied the correct filename.

However, the node is still created without an image. It doesn't appear that the temp image file is uploaded.
I can then edit the node, and attach a file.
So, images don't seem to upload properly when creating a node, but it does seem to work when editing a node that already exists.

This is why I thought it was mysqli related. I switched back to mysql after I had created a new image node with a failed attachment, then edited it and the attachment worked. So I was mislead into thinking it was the mysql/mysqli change and not simply an edit an existing vs creating a new node issue.

I've searched for the above error, and found quite a few posts, but none that seem to still apply. I'm using the latest (2007/10/29) dev release.

Thanks,
Nate

It appears to be a conflict with the actions module, but it seems to have stopped working only recently; image nodes have been functioning within our workflow for a while.

The actions we apply from (creation) -> FirstWorkFlowState are as follows:
1) Send e-mail to the user
2) Unpublish node (the default is upublished, this is just to make double-sure)
3) Send e-mail to the moderator

Simply disabling the workflow for image nodes is our work-around, but this can't be a permanent solution for us. We need to apply automated steps to all new nodes of any type.

Thanks,
Nate

No, it does not persist if the Unpublish Node action is removed from the first workflow transition.
Unfortunately, this is something I'd rather not remove without and I would need to create a whole 'nother workflow for just image nodes.
Images and Stories share the same workflow. Unpublish Node is there to help prevent user error; It helps to keep admins from publishing nodes before they reach the proper workflow state.

By the way, thanks for the responses guys, and sorry for the initial confusion.

Is this really a problem with actions, though? Story nodes in the same workflow have no problem with Unpublish Node in the first transition. This should also be reproducible. I have two sites with this issue.

Thanks,
Nate