-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.0] Consistent validation of the database name #24291
Comments
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. |
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 |
plesase test #39889 |
Closing as having a pull request. Please test #44623 . Thanks in advance. |
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
The text was updated successfully, but these errors were encountered: