No Code Attached Yet
avatar nbradshaw45
nbradshaw45
23 Feb 2022

Steps to reproduce the issue

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 ?

Expected result

An email should be sent for self-registration

Actual result

No email is sent

System information (as much as possible)

4.1

Additional comments

avatar nbradshaw45 nbradshaw45 - open - 23 Feb 2022
avatar nbradshaw45 nbradshaw45 - change - 23 Feb 2022
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 23 Feb 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 23 Feb 2022
avatar alikon alikon - close - 26 Feb 2022
avatar alikon
alikon - comment - 26 Feb 2022

please test #37149

avatar alikon alikon - change - 26 Feb 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-02-26 09:09:10
Closed_By alikon
avatar nbradshaw45
nbradshaw45 - comment - 26 Feb 2022

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)


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37128.

avatar redpanda-gr
redpanda-gr - comment - 3 Oct 2023

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

  1. a user is created (but activated)
  2. an email sent to the user and inform his that his account is up and run, no activation needed.

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!

avatar alikon
alikon - comment - 3 Oct 2023

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....

avatar redpanda-gr
redpanda-gr - comment - 3 Oct 2023

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 !

Add a Comment

Login with GitHub to post a comment