first apply #9493 to forbid a dob in the future while the User registration.
enable the plugin: User - Profile
and set date of birth as Required
Having for both cases (backend and frontend) the same error message.
Error messages are different if you register a new user on frontend or backend.
On backend we have an Error class="alert alert-error"
and on frontend we have a Warning class="alert"
.
Backend
Frontend
3.5.0-rc4 WITH #9493 applied
Status | New | ⇒ | Confirmed |
Category | ⇒ | Language & Strings Plugins |
Issue persist on 3.7-staging.
Still persists on 3.7.3-staging.
In the frontend and backend if the passwords don't match you get a 'red' error message so it would seem that to be consistent we should use an 'error' message in the frontend as opposed to a 'warning'.
If this is agreed then change line 177 of components/com_users/controllers/registration.php to read
`$this->setMessage($model->getError(), 'error');
@nibra - please review in a week to decide course of action
Status | Confirmed | ⇒ | Needs Review |
Status is set on "Needs Review".
Status | Needs Review | ⇒ | Pending |
Let us use error in back and frontend, back to pending
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-22 22:35:50 |
Closed_By | ⇒ | brianteeman |
I can confirm
...should be handled better from js side ?...