Skip to content

[configuration] No error when renaming a subproject to a name that already exists #7947

@ridz1208

Description

@ridz1208

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

image

To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):

  1. Go to the Configuration module -> Subprojects
  2. chose any subproject and edit its name to match another name in use
  3. hit submit

What did you expect to happen?
An error should be thrown saying that the subproject name is already in use

Metadata

Metadata

Assignees

Labels

24.0.0-bugsIssues or bug fix PRs that were raised during the testing of release 24.0.0Category: BugPR or issue that aims to report or fix a bugModule: configurationPR or issue related to configuration moduleState: Discussion requiredPR or issue that requires the resolution of a discussion with the relevant parties to proceed

Type

No type

Projects

Status

No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions