This email is already reserved to be used soon.

Slight Update – when i switiched of the “Email Confirmation” setting I stopped getting the error message “This email is already reserved to be used soon.
Please try a different one!“ but instead got a new error message “This email is already in use.
Please try a different one!” The user is created in the backend now though despite the error message.

Also I have set the login form to be Email only, however it still shows the Email and Password fields in the login form.

Sorry, I dont mean to spam however I have another update for you. I think I have made some progress here on trying to figure things out. I found all of the failed email registrations in the unconfirmed email address area. So that solved that issue. I have turned off the Email Confirmation for now.

I have turned on “Automatically Log In – Enable to automatically log in new users after successful registration.” But it doesn’t automatically log the user in, instead it give them the error “This email is already in use. Please try a different one!”?However an email confirmation is sent with the username and password.

I have installed the plugin to protect a specific page, I have placed the registration and login shortcodes in a block which I have embedded in the custom restriction message. Ideally Im thinking what should happen is they register and instead of the error they automatically can see the restricted page, in other words the restricted page gets revealed and the person still gets an email with their username and password. At the very least they should not get the “This email is already in use. Please try a different one!” message, instead they should get a message that says something like “we have received your registration please check your email for your username and password then return here to login.

I have set it so that Profile Builder creates the username and password the registration form just asks for First Name – Last Name and Email address.

To sum up I believe the error in the form is that it is not automatically logging the person in instead it gives an error message. I look forward to your response on this.

Hi @keithcreate108,

1. ?Could you please go to your site’s Dashboard -> Plugins -> Installed Plugins -> and send a full screenshot with everything you have installed related to Profile Builder (make sure the plugin version can be seen)?
2. Could you please go to your site’s Dashboard -> Pages -> edit the page where you have our Registration form -> and send a screenshot of exactly how the Registration form was added to the page?

You can use a site like https://snipboard.io/ to share the screenshots.

Best regards,

Hi I attach three screenshots. I am using the Flatsome theme which has the function of creating blocks. First I embed the forms in a block and then I add them to the page tha I want to restrict.

Further update. I have reconfigured the restricted page so that the registration form opens in a lightbox, when done this way the registration completes, the lightbox closes and the email gets sent. As this is a solution of sorts, (I would prefer to not have to put the form in the lightbox), I think the issue is that the registration form does not work when it is put into the “Messages for logged-out users” dialogue box. I would appreciate it if you can continue to investigate this please.

Hi @keithcreate108,

If you create a new page and on this new page you only add the [wppb-register] shortcode, does it work correctly? Also, try to use the default WordPress Gutenberg Editor when doing this test (while using the Shortcode block).

Best regards,

Hi Yes it works on a new page and it works in a light box but it does not work on the restricted page I had it in.

I’ve directly added the [wppb-register] shortcode to the Restriction message (“Messages for logged-out users”) and in my case it works correctly. Since this might be related to the Flatsome theme, more specifically to how it embeds the forms into blocks, I would suggest directly adding the [wppb-register] shortcode into the restriction message and checking if you still encounter this issue.

Yes I have already tried that also, and the same error occurred. Maybe the porblem, is the nature of the content that is on the restricted page. On that page there is a booking style form which, depending on how you arrive to the page may have content preloaded to it or not. For example there is a widgte on the home page which captures the initial inputs and when you submit it then it goes to the booking page which is the one with the [wppb-register] on it it als has a [wppb-login] on it too. If someone is already registered and logs in the page loads correctly with the output generated from the first step of entering the information on the home page. But this is not the case when the person registers for the first time.

Can you tell me what should happen when someone registers directly on the restricted page, does the page reload, does the form give a confirmation message that ena email has been sent/

Hi @keithcreate108,

Can you tell me what should happen when someone registers directly on the restricted page, does the page reload, does the form give a confirmation message that ena email has been sent/

-> If you add the PB Register form normally to a page, the process is the one you’ve mentioned, after submission the form reloads/refreshes, the confirmation message is shown and the email conformation email is sent.