If I try to add a new gallery with the same name as a gallery I deleted previously, I get this message:

"user warning: Duplicate entry 'galleries/#user#/#gallery#/feed-en' for key 'dst_language' query: INSERT INTO url_alias (src, dst, language) VALUES ('node/3679/feed', 'galleries/#user#/#gallery#/feed', 'en') in #site#\modules\path\path.module on line 112."

#user#, #gallery# and #site# are my replacement tags to remove site-specific information.

The gallery was created in spite of the error. The original gallery name was deleted under an earlier alpha version of the module, so it may just be something left over from one of those earlier installs. I'll try some more iterations and see if it causes problems with galleries created and deleted only under the newest version, and update the task if that generates any new info.

Comments

dddave’s picture

Version: 6.x-2.0-alpha7 » 6.x-2.0-alpha9

Stumbled upon the same issue just recently. The old gallery is resurrected somehow (noticed it because the creator was an old testaccount). Could be connected to #486750: File folder left behind upon gallery delete.

dddave’s picture

Version: 6.x-2.0-alpha9 » 6.x-2.0-alpha10

Issue still exists. It is even possible to create a gallery named like an existing gallery. The gallery is created but no pictures aren't uploaded. The original gallery can still be accessed and managed but you cannot upload new images.

kmonty’s picture

Priority: Normal » Critical

This is important enough that it should be fixed before the beta.

kmonty’s picture

Version: 6.x-2.0-alpha10 » 6.x-2.x-dev
kmonty’s picture

Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

I could not replicate the issue.

dddave - can you still get this to occur on a fresh installation?

dddave’s picture

Status: Postponed (maintainer needs more info) » Fixed

Testing:

1) Creating a gallery with a name of an existing gallery works well. The new gallery gets a number added so there seems to be no conflict (reported in #2)

2) OP seems to be solved, too.

Seems to be fixed.

Status: Fixed » Closed (fixed)

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