com_config is looser at validating the database name than the installer (which was patched as part of #23704). This should be normalised using a standard validation filter for JForm
Labels |
Added:
?
|
Title |
|
Status | New | ⇒ | Discussion |
Category | ⇒ | com_config |
Labels |
Added:
J4 Issue
|
Status | Discussion | ⇒ | New |
Build | staging | ⇒ | 4.0-dev |
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-11-14 10:51:05 |
Closed_By | ⇒ | joomdonation | |
Labels |
Added:
No Code Attached Yet
Removed: ? |
Status | Closed | ⇒ | New |
Closed_Date | 2022-11-14 10:51:05 | ⇒ | |
Closed_By | joomdonation | ⇒ |
I do want it because it's more about the security of what we are validating before trying to connect than whether it works or not
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-02-19 11:07:39 |
Closed_By | ⇒ | alikon |
Status | Closed | ⇒ | New |
Closed_Date | 2023-02-19 11:07:39 | ⇒ | |
Closed_By | alikon | ⇒ |
From what I see, that kind of validation is nice to have but not needed anymore. The reason is because before the change is saved, we even try to connect to database to see if it works before saving the change.
With that said, I'm closing this issue for now. Please re-open it if you still want to have this validation rule implemented.