Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#10 | imagecache_372643.patch | 934 bytes | drewish |
#7 | imagecache_fix-update.patch | 588 bytes | fernao |
Comments
Comment #1
Standart CreditAttribution: Standart commentedComment #2
gutomec CreditAttribution: gutomec commentedI have the same problem!
Comment #3
zd370 CreditAttribution: zd370 commentedyeah.. 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."
Comment #4
Standart CreditAttribution: Standart commented6.x-2.0-beta5 works for me.
Comment #5
fernao CreditAttribution: fernao commentedIt 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.
Comment #6
fernao CreditAttribution: fernao commentedwops, 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.
Comment #7
fernao CreditAttribution: fernao commentedThis check worked with me.
Comment #8
fernao CreditAttribution: fernao commentedComment #9
drewish CreditAttribution: drewish commentedare 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.
Comment #10
drewish CreditAttribution: drewish commentedmy bad. mis-read the bug report. committed the attached to HEAD.