Re-Send Double Opt-in Mail about femanager HOT 14 CLOSED

Nice idea but not planned at the moment.

from femanager.

Closed as in "I don't want that feature" or closed as in "I don't have time"? Thinking about a PR.

from femanager.

We're short before 4.0.0 release and will focus on that. Nevertheless PR are always welcome.

from femanager.

Hi Alex, I need this feature for one of my client's websites because nearly 20% of the users which try to register get stuck because they don't receive the e-mail (although we ruled out all possible deliverability issues). Would you be able to include this as a feature if we sponsor development?

from femanager.

Hi @moger-xx - this could be an idea for the BE Module (Frontend Users). We could add a new button to all pending registrations and try to resend it. Could that be a solution?

from femanager.

That would be good, but the primary goal was to offer it in the frontend so users can do it themselves and don't have to deal with customer service at all. I would like to offier it in the following places:

1. On the first confirmation view which is shown after the registration has been submitted by the user which basically says something like: "Thank you for your registration. We have sent you a confirmation link to your email [email protected]. Please confirm your registration by clicking on that link."

Now we would add something like: "Didn't reveice the e-mail?" with a Button "re-send confirmation email" and a remark "please also check your spam folder". Technically the best option would be that this button works via ajax, so the user does not have to leave the page and a success message shows up after the email has been sent again. If that's too much effort, a non-ajax solution (separate confirmation view) would also be acceptable.

2. Also we should show a link in the error message which says that an e-mail-address (username) is already taken. But only if the corresponding account has not been confirmed yet or is disabled, so we don't show the link when the corresponding account is working.

3. In our case, probably we should also show the link in the website's FAQ or below the registration form. But I think this is rather special so it does not need to be included but just be possible (viewhelper / extbase action).

from femanager.

But what happens, if the user closed the last view? Then we can't start the process again.

from femanager.

This should be covered by case number 3. We could link to a view containing a form, in which the user can enter the e-mail-adress (username) again and trigger the re-sending. of course the same restrictions apply as in case number 2. Think of it being somewhat like a password forgot functionality.

from femanager.

I try to summarize:

• We need an action, that enables a fe_user or and be_user to resend an open request (Double Opt-in E-Mail)
• We need an option for the Plugin, that an editor is able to decide, wether this option is shown or not, at view, after the first step of the registration is done
• We need an additional view ( Re-send Double Opt-in E-Mail), that an user is able to start this action and / or an detection during the regular registration, if this user exists.

Did I miss anything?

from femanager.

Sounds good :-)

from femanager.

@moger-xx can you send your contact data to stefan.busemann(at)in2code.de - then i can create an offer.

from femanager.

is released in 4.2.0

from femanager.

The Option
tx_femanager.UserBackend.confirmation.ResendUserConfirmationRequest = 1
needs to go into documentation.

Additonally, after activating it and opening the backend View, we got:

Sorry, the requested view was not found.
The technical reason is: No template was found. View could not be resolved for action "listOpenUserConfirmations" in class "In2code\Femanager\Controller\UserBackendController".

Reason is: the template "listOpenUserConfirmations" starts with a lowercase "l" but Uppercase "L" is expected on case-sensitive filesystems.

from femanager.

Also, the search form in the backend view "listOpenUserConfirmations" posts against the wrong action ("confirmation" instead of "listOpenUserConfirmations"), so search is not possible.

from femanager.