About Testing PilotPress
Applies to: ONTRAPORT Plus and above.
Creating a test contact and assigning it credentials to log into your WordPress site, and then logging in as that contact seems like a great way to test how well PilotPress is protecting your content. However, WordPress cookies the Administrator's browser and reads that cookie even in private or incognito mode. When you log in as your test contact you may see a login block on the page you should be redirected to, or a blank page. Depending on the "On Error Redirect to" setting on the protected page, you may be redirected to the home page or the standard login page.
This article provides some tips on testing the PilotPress integration properly.
Test Using Another Browser or Computer
For many people this is the easiest method. If you normally use Chrome, install Firefox and use it for your testing. For this to be successful, remember never to use the test browser to log in as the Administrator of the WordPress site. If you do, follow the steps below to clear the cookies for the site.
People like this method because it preserves their cookies on their working browser and allows them to log into their WordPress site easier for day to day work.
Clearing Cookies to Log In
Follow these steps to log into your WordPress site as a new user:
- In ONTRAPORT, create a new Contact for testing purposes. Add a Membership level to the contact. Keep ONTRAPORT open to this contact record.
- Open a new private tab or window in your browser (see instructions for Firefox and Chrome).
- In the private tab or window, clear the cookies for your WordPress site. This step is required. To see instructions on how to clear your cookies, see this article.
- Go to the default WordPress login page by adding "/wp-login.php" to the end of your domain.
- Log in as your new contact and verify the membership functions.
- To test a new membership level, log the contact out of WordPress. Add the new membership level in ONTRAPORT and log the contact back into WordPress.
If you have trouble, please chat Support for assistance.
Plugins That Conflict with PilotPress
Plugins reported to conflict:
- Any other "membership" plugin
- Any plugin that manages "redirection"
- Caching plugins
- All in One SEO
- Backup Buddy
- Page Expiration Robot or Scarity Samuri
- User Role Editor
- Login Form Editors (using redirection)
About Cache Plugins: PilotPress uses the WordPress database for member verification, but some caching programs will store protected pages in memory or as static HTML files on disk and display them to any visitor. You must exclude any protected member page from the cache to use these plugins. WP Rocket, WP Super Cache and W3 Total Cache and most other caching plugins have configuration options to prevent caching of pages or directories on your site. Add all of your PilotPress protected pages to the exclusion list.
WordPress has over 50,000 plugins and we are unable to test all of them. Symptoms of a plugin conflict include protected pages being visible to non-members, members having to log in again when navigating to another protected page, and content not being visible in the WordPress editor. If you find a conflict not listed above please contact Support and let us know.
Articles in this section
- WordPress Integration Overview
- Set up Membership Quick Start
- PilotPress Settings
- PilotPress and the WordPress Editor
- Integrate an Existing WordPress Site
- Integrate a New WordPress Site
- Migrate From Another Membership System to ONTRAPORT
- Creating Membership Levels
- Protect Content on Pages, Posts and Categories in WordPress
- Testing PilotPress Content Protection