Hi

I am having a little problem with this module. When I upload images, and press "next step" I come to a "Page Not Found". And when I look at the content, the uploaded pictures are not published.
I can not even select the "publish" checkbox when uploading.
What am I doing wrong? I really like this module...

Comments

Jacobtv’s picture

i now removed the "edit captions" permission, and now the images are published, but there is a

in the body field.
Do I have to enable some specific feature to edit captions with this module?

grandcat’s picture

Status: Active » Fixed

You didn't run update.php, this is the problem of most users. (see http://drupal.org/node/297805 to solve the problem). Just go to settings page (admin/settings/image/image_fupload) and save the form. Now, no 404 error should be displayed any more on clicking "Next step".
If you have enabled the feature "edit captions", it's not possible to choose "publish..." because this step will be done later after editing captions.
If there are any further problems, try to use beta-version.

Jacobtv’s picture

Thank you very much. That did it. Already thought I did it, but did it again, and it worked so... Thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

AxelBernhardt’s picture

I still have this same problem. and i tried
6.x-3.0-rc2 2009-Apr-08
6.x-3.x-dev 2009-Apr-09

I am a bit confused, as I believe I have seen node/add/image/list_images yet.
And I believe, I had seen some admin page for editing the next step thing.

Cannot find these, please help.
Changing the "edit captions" permission did not change anything for me, sorry,

now i hit the reset settings button in /admin/settings/image/image_fupload
and I got node/add/image/list_images back !!

Sorry, this seems to be a kind of bug. (Although this mod is great, thanks for that!)
Cause there seems not to be visible in the settings page, what caused the problem.

maverick14’s picture

I also had this issue, even in the latest version (3.0 RC2). The issue is fixed when I hit the 'reset to default' button. Like suggested in #5. Good post AxelBernhardt.