Get Started
Paid Memberships Pro – Import Users From Csv Integration icon

12 versions

Paid Memberships Pro – Import Users From Csv Integration history.

Every release of Paid Memberships Pro – Import Users From Csv Integration is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.

11 of 12 releases scanned clean
v1.5.3Latest
October 12, 202638.6 KBScanned
Fixed
  • Fixed an issue where blank CSV values overwrote existing user data when updating users using their user ID and having skipped values in other columns. Blank values are now skipped. A value of `0` can still be used to clear the first name, last name, website, and biographical info fields. #95 (@andrewlimaza)
  • New users imported with a blank role are now given the site's default role instead of no role. #95 (@andrewlimaza)
October 1, 202637.9 KBScanned
* SECURITY: Removed an unused parameter on the import resume screen that could reset an in-progress import. #93 (@dparker1005) * SECURITY: Improved sanitization and escaping throughout the plugin to resolve Plugin Check security findings. #92 (@dparker1005)
v1.5.1Unavailable
September 26, 202636.7 KBScanned
Other
  • SECURITY: Importing users now requires the `manage_options` capability (or `manage_network_users` on multisite). Use the new `pmproiucsv_import_capability` filter to change this. #90 (@dparker1005, @kta1kri)
Added
  • The import mapping screen now groups PMPro user fields by their field group. #88 (@dparker1005)
Fixed
  • Imported memberships with an inactive status or a past end date are now deactivated via `pmpro_cancelMembershipLevel()` so membership change actions fire, instead of a direct database update that left integrations such as LearnDash with access still granted. #89 (@andrewlimaza)
  • Fixed an issue where passwords for users matched by the ID column were saved unhashed when "Update Existing Users" was not checked. #90 (@dparker1005)
  • Fixed an issue where the first character of the first row in each import batch after the first was skipped, which could import users with incorrect data. #91 (@dparker1005)
v1.5Unavailable
September 14, 202635.2 KBScanned
Added
  • The membership_id column is no longer required. CSV files without a membership level can now be imported to create or update users without changing their membership. #85 (@andrewlimaza)
  • Add PMPro User Fields to mapping screen dropdowns and automatically detect if header matches the User Field key. #86 (@flintfromthebasement)
August 25, 202634.9 KBScanned
Added
  • Normalize date-type User Fields to Y-m-d format when importing. #82 (@flintfromthebasement)
v1.4.0Unavailable
August 20, 202634.7 KBScanned
Other
  • SECURITY: Improved security to harden against potential vulnerabilities. Defensive coding practices have been applied to prevent XSS while importing users. #82 (@flintfromthebasement)
Fixed
  • Fixed an issue where order timestamps would always default to current date of import. #81 (@LSNicholls)
  • Fixed an issue where 'id' would not automatically map to 'ID' in the field mapper. #80 (@andrewlimaza)
  • Fixed an issue where the "Skip Existing Members" option was not being honored when looping through batches. #83 (@dwanjuki)
v1.3.0Unavailable
July 31, 202633.2 KBScanned
Added
  • Added compatibility for multi-value User Fields importing. If a User Field is set to allow multiple values (multiselect,checkbox_grouped etc), the import will now accept a comma-separated list of values for that field. (@flintfromthebasement,@andrewlimaza)
v1.2.2Unavailable
May 15, 202632.2 KBScanned
Fixed
  • Fixed an issue where imported members were expiring one full day early because their end date was stored with a `00:00:00` time and the daily expiration cron cancelled them at the start of that day. End dates without an explicit time are now padded to `23:59:59` to match PMPro core's checkout behavior. #74 (@camilolunacom)
  • Fixed an issue where error log line numbers reset to 1 at the start of each batch during batched imports, making it hard to tell which CSV row produced each error. The line numbers now track the absolute file row across all batches. #73 (@JarrydLong)
v1.2.1Unavailable
March 20, 202631.7 KBScanned
Added
  • Added additional aliases for subscription and payment ID's.
Fixed
  • Fixed an issue where Custom User Meta fields were not correctly importing.
v1.2Unavailable
March 13, 202632.3 KBScanned
Added
  • Added a field mapper logic to allow users to map their CSV columns to the correct fields in PMPro. This allows for more flexibility in the CSV format and can help avoid issues with column headers not matching expected values. (@andrewlimaza)
  • Only allow AJAX import method to prevent timeouts for large CSV files. (@andrewlimaza)
  • Added "DOING_PMPRO_IMPORT" constant during import process to allow for custom code to check if an import is currently running. (@andrewlimaza)
  • Added better support for Paid Memberships Pro v3.5+ and utilizing the restricted folder logic to store files. (@andrewlimaza)
Fixed
  • Adjusted the wp_new_user_notification as an argument was deprecated and no longer used.

Why archive

Sometimes the latest release isn't the one you need. The archive lets you pin Paid Memberships Pro – Import Users From Csv Integration to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.