[configuration] No error when renaming a subproject to a name that already exists #7947
Labels
24.0.0-bugs
Issues or bug fix PRs that were raised during the testing of release 24.0.0
Category: Bug
PR or issue that aims to report or fix a bug
Module: configuration
PR or issue related to configuration module
State: Discussion required
PR or issue that requires the resolution of a discussion with the relevant parties to proceed
Milestone
Describe the bug
If you rename an existing subproject to a name that is already in use by another subproject, a 500 Error is thrown in the apache error log but no feedback is given to the user, instead the page is simply not updated, not freshed and the change seems to have taken effect until you reload the module
To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):
What did you expect to happen?
An error should be thrown saying that the subproject name is already in use
The text was updated successfully, but these errors were encountered: