After creating a user using the api - an email is NOT being kicked off to the new user.
Create User API documentation: https://documenter.getpostman.com/view/ ... 8340d77e4f
Joomla Settings:
New User Account Activation = 'SELF'
Send Password = 'Yes'
I was hoping that an email will be sent to the user with their password using the Mail Template: 'Users: New account with self-activation (with PW)'
Is this a bug? Or is this just not ready yet? Or is this how it was designed to work? Can there be another option in the JSON to kick off the email if it is set to: 1 ?
An email should be sent for self-registration
No email is sent
4.1
Labels |
Removed:
?
|
Labels |
Added:
No Code Attached Yet
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-02-26 09:09:10 |
Closed_By | ⇒ | alikon |
Thank you! This tested good!
However, I have a suggestion:
"sendEmail": (0 or 1) relates to receiving admin messages (the name is a little confusing).
I think it would make sense to add a new flag for send email to users on create - so that it is optional - there could be reasons why an admin may not want to send these emails.
So creating a new json element called "sendUserWelcomeEmail": values (0 or 1)
Hello J! team.
Probably, I'm not sure about the flow of this issue.
If I create a user using API, I have the next results
But if I have at config "New User Account Activation" as SELF and try to create a user, again from API, I have the exactly previous results!
A user is created, but already activated! No email sent with the activation link, only the email that his is already activated.
There is something in the flow that I cannot understand? This is the right code flow for the API at user creation with SELF activation?
Best regards,
Redpanda
I'm really sorry for my bad English!
dunno what should be the "correct" behaviour from a web service,
imho prefer to not set self-register mode from webservices, but,
if we would like to "mimic" the cms....
Thank you for your response!
The truth is that I don't know what a web-service should do and what not, in order to not mimic a CMS.
My comment was based on, since we have a hook (email send) for the endpoint
POST /users
we could have one more, lets say
PATCH /user/verify/{id}
Imho the SELF activation is an important step for the registration process, but of course I understand that the API should be "to the point".
Thank you again @alikon !
please test #37149