When you go to: admin/build/imagecache/1 (e.g. your first "created" preset) and you modify something.. e.g. the order of the actions, then you click the update button it spits a warning message: "The namespace you have chosen is already in use." + your change is not updated.

Files: 

Comments

Standart’s picture

Title:update button doesn't work» Can't update preset
Component:User interface» Code
Priority:Normal» Critical
gutomec’s picture

I have the same problem!

kris84’s picture

yeah.. i got the same warning when i tried to switch the order of my actions in one of the presets

"The namespace you have chosen is already in use."

Standart’s picture

6.x-2.0-beta5 works for me.

fernao’s picture

It happens only while editing a preset without changing it name

access you preset:
- http://yourhost.org/admin/build/imagecache/1
- just click on 'update preset'

and it will raise the error 'The namespace you have chosen is already in use.'

This part of the bug it's almost ok.

The problem is when you update it to a similar name. The apache enter in a kinf of loop I think, because my processor goes to 100%, and I think the only way to stop it is by restarting it! :(

I experienced other errors while accessing theses messed presets like other errors. I think a good testing is by altering the names of the presets and try to override names that already exists.

fernao’s picture

wops, my mistake when I talk about the second part (user can overwrite). No, user cannot overwrite.

The bug is ony that of cannot save with the same name.

fernao’s picture

Status:Active» Needs work
StatusFileSize
new588 bytes

This check worked with me.

fernao’s picture

Status:Needs work» Needs review
drewish’s picture

Status:Needs review» Closed (duplicate)

are you sure this is still a problem in the -dev release? it should have been fixed in #356668: Validation problems with imagecache_ui_preset_add_form.. i think this is really a duplicate.

drewish’s picture

Status:Closed (duplicate)» Fixed
StatusFileSize
new934 bytes

my bad. mis-read the bug report. committed the attached to HEAD.

Status:Fixed» Closed (fixed)

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