When it asks if existing or new Gallery, then the new Gallery does not ask for the name!
The bug appeared after upgrade to new image module+drupal 6.14

CommentFileSizeAuthor
#8 imgupload.module.newgallery.01.diff646 bytesbhagman

Comments

workonwomen’s picture

workonwomen commented

Any update?
If I click on New Gallery button it comes back with the warning:
"Please select a name for the new gallery."

But there is no form for that...
Tried to debug, but failed, any help?

kristofseyen’s picture

kristofseyen commented

i have the same problem, still couldn't figure it out.. it was also after the update to drupal 6.14

sahuni’s picture

sahuni commented

Is this module still maintained?
I'd like to use it, but I have the problem mentionned up and also the upload does not work.
If it's no more maintained, tell please, so I look for another module

kristofseyen’s picture

kristofseyen commented

i'm having the same problem here... "Please select a name for the new gallery." no errors in the java console

briandmiller’s picture

briandmiller commented

Same problem here with new installation.

sahuni’s picture

sahuni commented

I let it down. I use photos module.

rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented
Priority: Normal » Critical

+1 Subscribing...

bhagman’s picture

bhagman commented
StatusFileSize
new imgupload.module.newgallery.01.diff646 bytes

Haven't checked it over 100%, but this check in the validate hook looked completely unnecessary to me:

if ($choice == IMGUPLOAD_CREATE_NEW_GALLERY) {

Attached a diff to remove the check and the subsequent bail-out (error).

Definitely needs to be checked.

b

Vincent Groen’s picture

Vincent Groen commented

I had exactly the same problem.

I confirm that the diff in #8 works (I manually added "//" in all lines described (in imgupload.module file)).

In this new setting, I tried to create a new image gallery and it worked. Then I uploaded some pictures in this new gallery, and this worked too.

So, I don't know if this line of code is really necessary, but without it, it seems to work fine! So (most probably) the code can do without this check (and error).