This post will help to troubleshoot a few common issues that can crop up at checkout when using Paid Memberships Pro with Stripe. Specifically, these troubleshooting tips will help if you receive one of the following errors at checkout:
- Please complete all required fields. (Even though you did fill out all fields.)
'Stripe\PaymentMethod' not found
PMPro v2.1+ altered a few things about how the checkout page runs. One update was to allow the “Terms of Service” checkbox to stay checked when there are other checkout page errors (e.g. a required SCA authorization). If you are using a plugin or theme with a custom PMPro checkout template, you may need to update that plugin or theme. Continue reading to learn how to update your custom checkout template to support this new structure.
This guide provides troubleshooting steps if your site is failing to create user accounts at checkout.
The same troubleshooting steps apply when your site is successfully processing membership payments or freezing at checkout entirely. You will know that this is happening if users report a white screen at checkout or if you see Orders in the Memberships > Orders admin page with the “User” listed as
Paid Memberships Pro can be used to set up membership levels with many different pricing structures. You can configure a level to offer a recurring subscription or a level with a one-time payment and expiration date. Unless you really want a membership to expire after a certain time frame, you usually DO NOT want to set BOTH a recurring billing amount AND an expiration date on your levels.
Many development and staging sites want to restrict total access to the site’s folder on the webserver. One of the easiest ways to do this is by setting a UNIX password at the server level.
This advanced developer recipe shows you how to set up custom
.htaccess rules to allow your Webhook or IPN data through this security measure. This will allow you to properly configure and test payment gateways in Paid Memberships Pro.
Page builders are a popular way to create a more visually appealing user experience on your site. Many Paid Memberships Pro users are confused with how to properly use these tools alongside the required shortcodes on various pages of your membership site, such as the pricing page or membership account page.
This post covers how to resolve conflicts between plugin shortcodes and popular page builders such as SiteOrigin Page Builder, Elementor and Beaver Builder.
We have long recommended Theme My Login as a very useful plugin for sites running Paid Memberships Pro. With features including themed login, frontend user profiles, and simple redirection rules, we found TML to be a great addition for any membership site. We recommended it to 100% of our users and included it in our WordPress bundle.
With the release of version 7.0+ of Theme My Login, several key features that were once included in the WordPress.org repository version of the plugin are now offered as premium extensions. This post details some short and long term options for membership site owners concerned about the changes and the best steps to take.
Is your site no longer working? Has your WordPress site been replaced with a blank white screen, the infamous White Screen of Death? Maybe you are experiencing styling issues, your footer is not loading correctly, or you are having a tough time checking out of your site. This is not unique to Paid Memberships Pro and can occur on any website, using any theme or any plugin(s). Knowing what is causing the problem can give you or a developer the relevant information needed to help fix these issues.
Whatever the reason, this article will explain how to enable debugging mode in WordPress to uncover any PHP errors or warning messages that are on your site.
Using Paid Memberships Pro in your selected payment gateway’s “testing/sandbox” mode allows you to test membership checkout without processing real payments. Sandbox mode requires unique credentials that vary based on the active payment gateway.
This post covers how to set up your test or sandbox account so that you can run tests on a membership checkout.
Some sites report “off by one day” errors when calculating end dates on new orders and memberships. What this looks like on the front end is setting someone’s end date to January 31, 2017 and then having it show up as January 30, 2017. Or expiration is set to happen at 12:00am, but it happens at 10:00pm instead.
This post covers some common reasons why this is happening and a collection of ways to set the various time stamp settings in your web stack, including your WordPress site, server operating system (CentOS/Linux), server’s Apache/PHP settings, and database MySQL settings.