PilotPress is a membership plugin created by Ontraport, it lets you build a membership site in WordPress, and you can create a portal where customers can manage their Ontraport orders.
PilotPress also allows you to host a partner center in WordPress, where partners can view their earnings and update their personal information.
WP Fusion is tested with PilotPress and the two plugins can be used together, but it’s recommended not to use PilotPress if you can avoid it.
#Difficulties with PilotPress
The main problem with PilotPress is that it authenticates user logins against the members portal in Ontraport, not WordPress.
This introduces several complications:
- Someone can log into WordPress, but not be logged in to PilotPress. They may have to log in a second time to access their customer portal or partner center.
- PilotPress can only understand user logins via /wp-login.php or a page with the [login_page] shortcode on it. If someone logs in via WooCommerce or another membership plugin, PilotPress will not recognize them.
- PilotPress needs to connect to Ontraport to authenticate logins, meaning if Ontraport is slow or the API is offline your users won’t be able to log in.
- Because passwords are stored in Ontraport, your users may end up with two different passwords, one for WordPress and one for PilotPress. This creates some complicated scenarios with passwords that need to be planned for:
- If someone resets their password via WooCommerce or another plugin, and tries to log in via a PilotPress login form, their login will fail.
- If someone resets their password via PilotPress and tries to log in via WooCommerce or another plugin, their login will fail.
- If people have been logging in via PilotPress and you deactivate the PilotPress plugin, WordPress will revert to handling logins. Because their WordPress password is different than their PilotPress password, users may need to reset their passwords before they can log in again.
#Using WP Fusion with PilotPress
There are a few strategies for using PilotPress depending on the complexity of your site.
#Very simple website
If you have a very simple website, i.e. no ecommerce plugins and no membership plugins, you can let PilotPress manage all user accounts. In this scenario you need to make sure that the only page you’re using for login is either the standard /wp-login.php, or a page with PilotPress’ [login_page] shortcode on it.
Anything that customizes the login process (i.e. LoginPress) will likely interfere with PilotPress. Likewise anything that affects login security (i.e. iThemes Security or WordFence), may prevent password resets from working.
In this scenario all logins are handled by PilotPress and passwords are checked against the members center in Ontraport. To reset a user’s password, you need to reset it in Ontraport via the members center, or the user must click the Forgot Password link on the PilotPress login form.
Password resets in the WordPress admin or via a WordPress reset password link will not work.
Once the user is logged in they will be able to access their PilotPress Customer Center or Partner Center.
WP Fusion will still recognize a user who has logged in via PilotPress and can unlock content using Ontraport tags and apply tags normally as if it were a real WordPress login.
#More complex websites
If you’re selling anything on your website via WooCommerce or another ecommerce plugin, delivering courses using an LMS, or running a membership plugin (i.e. BuddyPress) you will probably want to bypass PilotPress’ login process.
The reason is that a user may have one password for PilotPress and another for WordPress. So if they’ve reset their password via the PilotPress [login_page] shortcode and then come back later to make a purchase in WooCommerce, that password won’t allow them to log in to WooCommerce.
They will then reset their password for WooCommerce and the rest of WordPress, but later be unable to log into PilotPress until they reset their password yet another time.
The first question is, do you need PilotPress at all?
If you’re not using the PilotPress customer center or partner center, then the best solution is to deactivate PilotPress and let WordPress handle logins.
#If you do need PilotPress for some features
If you need PilotPress for some features, first you need to establish control over where people are logging in to avoid passwords getting out of sync.
For example if you’re running a WooCommerce store, you can remove the PilotPress login page and block access to /wp-login.php so people can only log in via WooCommerce’s My Account page.
Then if you need PilotPress in order to let your partners access their partner center and see their earnings, you can send your partners directly to the Affiliate Center page on your site, which includes its own PilotPress login form. This reduces the chances of regular users using the wrong login form.
To simplify things further, one solution is to have a separate contact record in Ontraport for each partner with a unique email address (separate from their normal user account on your site).
Then you can tell your partners that to access their portal they can go directly to the Affiliate Center page on your site and log in with the username and password you generated for them in Ontraport. This way your partners have two accounts: one for your affiliate area and one for the rest of your site, and will hopefully reduce confusion about which account to use on which login form.