nico80

Register Flow gives a simple solution to custom registration form needs. Rather than having you learn to use a new form designer, shortcodes are provided to turn your custom pages into registration steps. Action and filter hooks are then used to let plugin users tweak the registration process as needed. This is intentionally a developer focused solution to allow full control of the process.
The registration process has 3 steps:
<ul>
<li>Step 1 is where users could enter a username and validate there it is valid. You can implement custom validation to modify this step.</li>
<li>Step 2 would be the rest of the information (password, phone, etc). Once they complete this step an email will be sent enabling them to complete the process. You can implement custom validation here as well.</li>
<li>Confirmation step is called when the user clicks on the link in their email (up until that point they have not actually been created as a WordPress user). You can implement custom validation as well as custom logic to be run when the user has been created (good place to save some additional user data).</li>
</ul>
All these steps are controlled via custom pages, action hooks and filters – see the FAQ section for more details.

F1 Register Flow

Register Flow gives a simple solution to custom registration form needs.  Rather than having you learn to use a

Ipstenu (Mika Epstein)

We’ve all had this problem: a group of spammers from <code>mail.ru</code> are registering to your blog, but you want to keep registration open. How do you kill the spammers without bothering your clientele? While you could edit your theme’s <code>functions.php</code> and block the domain, once you get past a few bad eggs, you have to escalate.
Ban Hammer helps you do that by preventing unwanted users from registering.
On a single install of WordPress, instead of using its own database table, Ban Hammer pulls from your list of prohibited emails from the Disallowed Comment Keys feature, native to WordPress. Since emails never equal IP addresses, it simply skips over and ignores them.
On a network instance, there’s a network wide setting for banned emails and domains. This means you only have one place to update and maintain your blocked list. When a listed user attempts to register, they get a customizable message that they cannot register.
For advanced documentation, including how to use on WooCommerce, please visit <a href="https://github.com/Ipstenu/ban-hammer/wiki" rel="nofollow ugc">the Ban Hammer Wiki</a>.
<ul>
<li><a href="https://github.com/Ipstenu/ban-hammer/" rel="nofollow ugc">Development</a></li>
<li><a href="https://github.com/Ipstenu/ban-hammer/wiki" rel="nofollow ugc">Wiki</a></li>
<li><a href="https://ko-fi.com/A236CEN/" rel="nofollow ugc">Donate</a></li>
</ul>
<h4>Privacy Policy</h4>
This plugin does not track data outside of what WordPress already collects. It utilizes the submitted email address to validate the domain and compares it to the list of prohibited domains and emails. No additional data is processed.
<h4>Credits</h4>
Ban Hammer is a very weird fork of <a href="http://www.joeswebtools.com/wordpress-plugins/no-disposable-email/" rel="nofollow ugc">Philippe Paquet’s No Disposable Email plugin</a>. The original plugin was a straight forward .dat file that listed all the bad emails (generally ones like mailinator that are disposable) and while Ban Hammer doesn’t do that, this would not have been possible without that which was done before.
Many thanks are due to WP-Deadbolt, for making me think about SQL and TTC for StopForumSpam integration. MASSIVE credit to Travis Hamera for the StopForumSpam/cURL fix! And then props to Helen Hou-Sandí for not using curl at all. Protip? Use <a href="http://planetozh.com/blog/2009/08/how-to-make-http-requests-with-wordpress/" rel="nofollow ugc">WP_http</a> instead!

Ban Hammer

Prevent people from registering via your disallowed comment keys.

F1 Register Flow vs Ban Hammer