Using another registration plugin

Turning it on

On the Settings tab, under Registration method, choose I'm using another registration plugin. Then put that plugin's form on your registration page instead of the [banginvites_form] shortcode.

That is the whole change. Nothing else needs configuring.

What stays exactly the same

• You still invite people from the Invite tab, and still choose the role each one gets.
• Links are still single-use and still expire on your schedule.
• Tracking still shows Pending, Accepted and Expired, with resend, new link, copy link and delete.
• The invitation email is still yours to write.
• The invitation-only page guard still protects the page.

What changes

Acceptance stops being something the form does and becomes something the plugin notices. WordPress announces every new user, whoever created them, and Bang! Invites listens for that announcement.

When a new account appears whose email address matches a pending, unexpired invitation, the plugin marks that invitation accepted, applies the role you invited them with, and sends the welcome email and your team notification exactly as it would have done otherwise.

Deliberately, it does nothing else. No redirect, no output, no interference. The other plugin may be halfway through an AJAX submission or about to show its own confirmation step, and everything after the form is submitted belongs to it.

Prefilling the email field

Every invitation link carries the invited address as an email parameter in the URL. Nearly every form plugin can populate a field from a URL parameter, and setting that up is the single most useful thing you can do in this mode. It removes the retyping, and with it the mismatch.

Look for a feature called prefill, pre-population, dynamic default value, or query-string population, depending on the plugin, and point it at the parameter named email. Making the field read-only afterwards is a sensible extra step, though the invitation itself is what enforces the address, not the field.

Who enforces the single use

The page does. The built-in form used to validate every link as it rendered; another plugin's form has no idea invitations exist, so the guard on the registration page takes over that job. It validates the link on every load, before the page is shown.

So the moment an account is created, validation starts failing and the link is dead, whichever plugin created the account.

Settings that go grey

Three groups of settings belong to the built-in form and have nothing to act on in this mode. They are dimmed rather than hidden, so you can see what you are not using and get it back unchanged by switching methods again:

• The registration form's colours, label, position and corner radius.
• Where to send people the first time, right after they register.
• Log people in automatically once they finish registering.

All three are now your other plugin's business. Set the post-registration destination and the auto-login behaviour there.

Two emails, one registration

Most registration plugins send a confirmation of their own. With the welcome email also switched on, a new client gets two emails within a second of each other saying much the same thing.

Pick one. Either turn off Send a welcome email on the Welcome email tab, or turn off the other plugin's confirmation. The tab shows a reminder about this while the other registration method is selected.

Adding somebody by hand still counts

The listener responds to any new user, not only ones created by a form. If you add a user under Users > Add New with an address that has a pending invitation, that invitation is marked accepted and the role you invited them with is applied. This is intended: it means the tracking list stays true no matter how the account actually came about.

Next

The FAQ covers the shorter questions.