Hello. Thank you for contacting the Toolset support.
Well - It's hard to say from where your current registration form is rendered theme/plugin. Basically - You should hide/remove the existing form which displayed from your theme or any plugin you are using. Then, Create a new registration form using Toolset Forms plugin.
The default WordPress registration form will be displayed at site.com/wp-login.php?action=register
If you create a custom registration form with Toolset that means adding it to a static page, e.g. site.com/register
You create a link for users to register (e.g. in your page header) that points to that static page, and you don't link to the normal WordPress registration form from anywhere, so users don't see it.
What is it that you are trying to do that is different from the above?
Thanks for your lucid reply. It makes things simple.
However, there's couple of things here.
a) I am using elementor, and they have a login widget, which opens up the defacto wordpress login/register url. So was wondering if there was a way to replace that url with toolset url. But I guess that question should go to elementor.
b) I want to ensure that the email that people enter when they fill up a registration form, belongs to them. For that I want to send a link on email, clicking on which should verify that the email address is indeed theirs and then they can be redirected to login. I had asked that on a separate thread and I am sure it can be done, so I thought let me ask if you could guide as to how we can use the toolset notifications system to do the same.
I'm not sure what customisation is possible with the elementor login widget, but from your description it sounds like you should make a registration page and then simply insert a link to that page, rather than use a login widget at all.
The second question sounds somewhat redundant. If you autogenerate the username/password with the registration form and send them in a notification to the email address specified in the registration form, then the email address *must* be valid or the user can't access the site.
Ouch. You are so right Nigel. I am sorry. Guess sometimes things right in front of our eyes create a blind spot. Thank you on both the inputs that you provided.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
