[#19068] - [4.0] Wrong message on creating a new user.
- Closed
- 14 Dec 2017
- Medium
- Build: 4.0.0-dev
- # 19068
Steps to reproduce the issue
Try to create a new user in Administrator area.
Expected result
Message to be popup.
1Notice
Could not instantiate mail function.
2Message
User saved.
Actual result
Message popup
Error
Save failed with the following error: Could not instantiate mail function.
System information (as much as possible)
PHP version: 7.1.11
Joomla! 4.0.0-dev
Additional comments
In both, the cases the new user is created.
joomla-cms-bot
- | Status | New | ⇒ | Confirmed |
That is the expected behaviour if you are working on a test environment that is not configured to send mail. Please test the mail sending functionality in the global configuration. If you can confirm that the test in global configuration works then we have a bug. If it doesnt work then its because your test environment is not configured for mail in which case Perhaps we need a better error message - something like "unable to send mail - please check your configuration"
Its about Error Message "Save failing …" but User is saved.
yes the message is wrong but please confirm if the test site can send emails or not
sorry, wasn't clear: I confirm only wrong Message, the Test-Environment is not configured to send E-Mails.
@brianteeman ,I known but it's about error message save failed but the user is created.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19068.
| Status | Confirmed | ⇒ | Discussion |
Sorry I was concentrating on the second part of the message not the first. mea culpa
I will take a look at fixing this over the next few days if no one beats me to it
Comparing it to Joomla 3 it looks like joomla 4 is outputting all messages in the queue inside the same alert output
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-14 22:28:24 |
| Closed_By | ⇒ | brianteeman |
OK its a more complex issue that this is exposing. I will create a new issue explaining it
Issue confirmed.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19068.