Updating WP Full Pay

To update a WP Full Pay plugin, follow these steps:

1. Log into your WordPress site.
2. Navigate to the 'Plugins' menu on the dashboard.
3. Click the 'update now' link next to the WP Full Pay plugin. WordPress will automatically download and install the update.

WP Full Pay includes major improvements such as the transition from the older "Stripe Elements" to the newer "Stripe Payment Element", enhancing the user interface and allowing customers to select their preferred payment method easily.

Additionally, we've upgraded to Stripe Connect for a more secure Stripe connection and easier support for your Stripe setup.

The current setup is designed to let you keep using your existing forms until you complete the Connect setup.

• In the WordPress admin, go to Full Pay → Settings.
• Open the "Stripe account" card in the Settings overview.
• Set the Account Mode toggle to Live, click "Connect with Stripe", and follow the redirection to Stripe.
• Log in with your Stripe credentials during the onboarding flow and select your existing account.
• Complete any required steps in the Stripe onboarding process.
• Switch the Account Mode toggle to Test, click "Connect with Stripe" again, and provide any additional information needed.
• Your existing forms and other configurations will continue to work as before.

Note: If you use the Members add-on or have custom code relying on hooks, review the Add-on and custom hook configuration section for compatibility.

WP Full Members is a separate plugin. Updating WP Full Pay does not update it, and both plugins must be current to work together. An outdated WP Full Members add-on cannot read current Stripe subscription data and shows January 1, 1970 as the next billing date for every member.

If you installed WP Full Members before WP Full Pay moved to Themeisle licensing, your copy of the add-on does not receive update notices. Its version number can even be higher than the current release, so do not use the version number to decide whether it is current. To replace it:

1. Log in to the customer portal and download the current WP Full Members .zip file.
2. Install it as described in How to install WP Full Members?, then activate it with your WP Full Members license key.
3. Go to Full Pay → Members and confirm that the next billing dates match your members' subscriptions in Stripe instead of showing January 1, 1970.

Upgrading from older releases

If you're planning to upgrade your WP Full Pay from an older release, it's crucial to be prepared for significant changes, especially in relation to Stripe product integration.

Understanding the Changes

• A key update in current releases revolves around Stripe product handling, enhancing the overall functionality and security of your payment processes.
• Upgrading from older releases means you need to set up new Stripe products. If this step is skipped, your current forms might stop working correctly, leading to potential disruptions on your website.

Preparation for the upgrade

1. Before moving to the latest release, create and configure new Stripe products within WP Full Pay. This ensures a smooth transition and operational continuity of your payment forms.
2. To avoid disruptions, consider scheduling the upgrade during a period of low activity on your site. Allocating downtime or choosing off-peak hours for the update can prevent significant impacts on your site traffic and user experience.
3. Always back up your website before proceeding with the upgrade to make sure you have a restore point in case of any unforeseen issues during the transition.

Reports only include payments that WP Full Pay records after its reporting data starts on your site. Upgrading does not import earlier payments from Stripe, so a date range that reaches back before the upgrade can show fewer subscriptions and zero or incomplete revenue, even though those payments still exist in Stripe. To review older payment history, export your payments from Stripe.

For any assistance or queries during the upgrade process, don't hesitate to reach out to our support team.