View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0035915 | mantisbt | administration | public | 2025-05-05 09:21 | 2025-07-23 06:04 |
| Reporter | dregad | Assigned To | dregad | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.26.0 | ||||
| Target Version | 2.27.2 | Fixed in Version | 2.27.2 | ||
| Summary | 0035915: Updating a global config yields incorrect error message | ||||
| Description | Trying to add a new config option from adm_config_page.php yields ERROR_INVALID_FIELD_VALUE, e.g. This is incorrect, it should be ERROR_CONFIG_OPT_CANT_BE_SET_IN_DB. | ||||
| Additional Information | Regression caused by introduction of ConfigsSetCommand (0032258). | ||||
| Tags | No tags attached. | ||||
| related to | 0032258 | closed | vboctor | Add REST API for setting config options that are settable via database |
| has duplicate | 0036158 | closed | dregad | Wrong error message when trying to set an option that can't be set in database |
| related to | 0036164 | resolved | dregad | Impossible to delete a global config defined in the database |
|
MantisBT: master-2.27 9aeb54fb 2025-05-05 12:52 Details Diff |
Correct error code when updating a global config Now using ERROR_CONFIG_OPT_CANT_BE_SET_IN_DB instead of incorrect ERROR_INVALID_FIELD_VALUE Fixes 0035915 |
Affected Issues 0035915 |
|
| mod - core/commands/ConfigsSetCommand.php | Diff File | ||
|
MantisBT: master-2.27 fcfc9344 2025-05-05 12:53 Details Diff |
Fix typo and improve error message wording Issue 0035915 |
Affected Issues 0035915 |
|
| mod - lang/strings_english.txt | Diff File | ||
