Paid Memberships Pro – Approvals

Name: Paid Memberships Pro – Approvals 1.4
SKU: 10120
Price: 3.99 USD
Availability: InStock

Version 1.4

SKU: 10120

$3.99$59.00Save 93%

One-time payment · lifetime access to this file

Instant download after purchase
100% original, unmodified GPL file
Free lifetime updates on request
Secure Razorpay / PayPal checkout

Want the whole library?Get a membership and download any theme or plugin on the site.

Product details

Version on file: 1.4
Type: Plugin
Released: November 21, 2018

About Paid Memberships Pro – Approvals 1.4

Approvals is an add-on for Paid Memberships Pro. It is meant for sites where a signup should not unlock content automatically, so an administrator reviews each new member first. It needs Paid Memberships Pro installed and active, and it works through the PMPro membership levels.

The listing gives no feature list, so check the readme in the package for how approval is turned on and how pending members are handled. The file on record is version 1.4 from November 2018, even though the product slug says 0.1. Test it with your current WordPress and PMPro versions on a staging site.

Requirements

Paid Memberships Pro

Key features

Manual approval of members: Designed to hold new signups until an administrator approves them.
Works with membership levels: Approval applies to Paid Memberships Pro levels, so it fits a levels-based site.
Add-on to Paid Memberships Pro: It extends PMPro rather than replacing it.
Details in the package: The listing doesn't state notification emails or the approval screen; the readme covers them.

Is it right for you?

A good fit for

Professional or private membership sites that vet applicants
Communities where only approved people should see members-only content

Look elsewhere if

Sites that want instant access after payment, which PMPro already does by default
Sites that don't use Paid Memberships Pro

How to install Paid Memberships Pro – Approvals 1.4

1
Download the file
Open My Account → Downloads and download the product. If the archive contains several zips (documentation, child theme, licensing files), you need the one named after the product.
2
Upload it to WordPress
In your dashboard go to Plugins → Add New Plugin → Upload Plugin and choose the zip.
3
Install and activate
Click Install Now, then Activate. If an older or free copy is already installed, WordPress offers to replace it with the uploaded version.

Notes for this product

Install and activate Paid Memberships Pro first, then add this plugin.

Setup: using Paid Memberships Pro – Approvals 1.4

Activate Paid Memberships Pro. Make sure PMPro is active and at least one membership level exists.
Install the add-on. Upload and activate Approvals, then look for its option on the membership level settings.
Turn on approval for a level. Choose the level that needs review and save it.
Test with a dummy signup. Sign up as a test member, check what they see while pending, then approve the account and confirm access opens.

Common problems and fixes

“The link you followed has expired.” when uploading

Why it happens: The zip is larger than your server's PHP upload limit (upload_max_filesize / post_max_size).
How to fix it: Raise the upload limit in your hosting control panel, or unzip the file and upload the folder to wp-content/plugins with your host's file manager or SFTP.

“The package could not be installed. No valid plugins were found.”

Why it happens: The uploaded zip is a bundle (or a theme), not the plugin itself.
How to fix it: Unzip the download once and upload the inner zip named after the plugin.

“Plugin could not be activated because it triggered a fatal error.”

Why it happens: Usually a PHP version older than the plugin needs, or a second copy of the same plugin (for example the free version) still active.
How to fix it: Check your PHP version under Tools → Site Health → Info, deactivate any other copy of the plugin, and enable WP_DEBUG_LOG to see the exact error.

Licence or “updates unavailable” notices

Why it happens: The developer's licence key isn't included. Features that call the developer's servers (template libraries, cloud APIs, automatic updates) need it.
How to fix it: Everything that runs locally works without it. For a newer file, use Request an update from your account.