Paid Memberships Pro Documentation

Action Scheduler is a scalable, traceable job queue designed for background processing large sets of actions in WordPress. It is specifically built to be distributed within WordPress plugins to handle resource-intensive tasks without impacting site performance.

It functions as an extension to the standard WordPress do_action() mechanism by adding the ability to:

• Delay a hook to run at a specific time in the future.
• Repeat a hook on a recurring schedule.
• Pass unique data to each scheduled hook, allowing callbacks to perform specific operations based on that data.

It is used by high-scale plugins like WooCommerce Subscriptions to process millions of payments and webhooks.

Action Scheduler is a scalable, traceable job queue designed for background processing large sets of actions in WordPress. It is intended to be distributed within WordPress plugins to handle resource-intensive tasks without impacting normal site operations.

Conceptually, it acts as an extension to the standard WordPress do_action() function by adding the ability to delay and repeat hooks. It works by triggering an action hook to run at a specified time in the future. Each scheduled hook can include unique data, allowing callbacks to perform specific operations on that data. Hooks can also be scheduled to run on multiple occasions.

You can extend the core functionality of PMPro using a library of over 65 Add Ons. Common use cases include:

• Email Marketing: Integrate with platforms like Mailchimp.
• Social Login: Allow members to join using social media profiles.
• Affiliate Management: Manage affiliates via native Add Ons or third-party systems like AffiliateWP.
• Events: Manage members-only events using integrations with Events Manager, The Events Calendar, or Sugar Calendar.
• Page Builders: Enhanced design capabilities for Elementor, Beaver Builder, and others.

Paid Memberships Pro can be used in a WordPress Multisite network in several ways:

1. Standalone Mode: By default, PMPro acts as a standalone plugin for each site in the network, with independent levels, members, and settings.
2. Member Network Sites Add On: Allows members to choose a site name and title during checkout, automatically setting up a new network site for them.
3. Multisite Membership Add On: Allows you to manage memberships at the 'Main' Network site and use those memberships to provide or restrict access on other Network Subsites.

To install Paid Memberships Pro, download the plugin from the official website and install it on your WordPress site.

After activation, follow these steps:

1. Run the Setup Wizard: A brief wizard will appear immediately after activation to guide you through the initial configuration.
2. Configure Membership Levels: Define your pricing and access levels.
3. Set up Payment Gateways: Configure your preferred gateway (e.g., Stripe or PayPal) to accept payments.

For detailed instructions, refer to the Initial Setup Tutorial.

For deep technical implementation, refer to the official documentation at ActionScheduler.org:

• Usage Guide: Instructions for installing and using the library in your plugin.
• WP CLI Guide: Instructions for managing and running actions at scale via the command line.
• API Reference: A complete reference for all available API functions.
• Administration Guide: How to manage scheduled actions via the WordPress admin screen.
• Background Processing at Scale: Guidance on running the queue via the default WP Cron runner.

For detailed implementation and management, refer to the official documentation at ActionScheduler.org. Key resources include:

• Usage guide: Instructions for installing and using Action Scheduler in your plugin.
• WP CLI guide: Instructions for running Action Scheduler at scale via WP CLI.
• API Reference: A complete reference guide for all API functions.
• Administration Guide: How to manage scheduled actions via the WordPress administration screen.
• Guide to Background Processing at Scale: Instructions for running Action Scheduler at scale using the default WP Cron queue runner.

If you prefer not to use Composer, download the latest release from the Stripe GitHub releases page. To use the library, include the init.php file in your project.

require_once '/path/to/stripe-php/init.php';

Unit Testing

You can run unit tests using phpunit directly:

phpunit tests/unit/

Alternatively, if you have rake installed, you can use it to run tests across both hhvm and php interpreters:

rake test:unit

Development Environment

To build a Docker image containing all dependencies and enter a terminal for testing, use the provided Makefile:

make

Stripe requires TLS 1.2. If your system defaults to older versions (common on older CentOS/RHEL), you will receive an invalid_request_error. You can force TLS 1.2 by passing the CURLOPT_SSLVERSION option to a custom CurlClient.

$curl = new \Stripe\HttpClient\CurlClient([CURLOPT_SSLVERSION => CURL_SSLVERSION_TLSv1]);
\Stripe\ApiRequestor::setHttpClient($curl);