Thomas S

Hi,

I have a beta I’d like you to try, if you don’t mind. You will need to deactivate and delete the existing plugin iteration before trying to install the linked .zip file of the Beta version.

Keep in mind that this _is_ a beta and shouldn’t be used for importing production data at this time.

First of all, I don’t think you’re using this plugin (the Paid Memberships Pro Import Members from CSV plugin) since this plugin is currently at version 2.16.

This specific plugin (where you’ve reported this problem) is installed from the www.ads-software.com repository and not from the Paid Memberships Pro add-on page.

Regardless, your import file contains at last 2 different of errors that would prevent it from importing with either of the tools available for PMPro.

1) You cannot use the Membership Level label in the membership_id column
2) The membership_startdate values are using an invalid date/time format (it has to be a date using the full MySQL DateTime format).

The name change is a function of the file upload and shouldn’t be related to the error message you’re getting…

I’m spending some time this evening looking at the plugin to see if I can figure out what’s happening on your end.

Hi Liat,

I’m presuming you’re currently testing with version 2.16 of the plugin?

I’m not seeing the same error on my end, so something to check is whether or not the JS is working properly…

Are there any errors/warnings in the JavaScript console of your browser before/as you’re importing?

Hi,

Thanks for using this plugin!

Which version of it are you using?

Can you share an example of a row you’re trying to import (along with the header row used)?

Thank you for your patience. I’ll continue to tweak the plugin and will try to figure out why it’s deciding (in your case) the membership ID is invalid/incorrect.

FWIW, I believe I’ve fixed any issues with the new user notification message in my plugin that aren’t caused by external factors.

Examples being any anti-spam efforts of your hosting provider, anti-spam efforts by the recipients email host or other plugins on the web server that are taking advantage of the fact that the notification function is a pluggable function.

I _believe_, as far as I can control, this issue is now resolved.

I’ve made a few updates to the plugin (v2.10) and have been testing extensively with the file example you provided.

The file now imports (assuming you change the date/time formats and update the file per the other warnings in the error log once the import completes) on my testbed, including in a Multisite configuration.

For Multisite, make sure you’re importing on the site where Paid Memberships Pro is active and has membership levels defined that match the membership_id column values or else the plugin will not import that record (and should log that fact to the error log).

Thank you for your patience!

Hi,

Thanks for providing the import file sample. I’m seeing a problem with the date formats and with how you’ve configured the level/dates for the 1st & 2nd users in the sample file.

Basically, the first issue is that the date format is incorrect when the file is saved (It has to save in a YYYY-MM-DD HH:MM:SS format).

Secondly, having an enddate _and_ a recurring billing plan doesn’t really make sense (based on how PMPro is designed). PMPro allows the combination because it’s a way to sort of implement a payment plan: i.e configure recurring payments until a # of payments, then leave the membership level active until the enddate. A simple “recurring billing setup would be expected to be terminated manually by either the user or an admin (via the Cancel page if the user is cancelling, or their profile if it’s the admin doing the cancelling).

However, the date/level configuration mismatch is _not_ why the membership record isn’t showing on the Members List (it will/should only trigger a warning).

I’m troubleshooting the reason why the membership_status seemingly isn’t being reflected correctly in the DB. That _is_ why your members aren’t showing in the Members list (the plugin is clearing the value for some reason).

Once I’ve fixed that I’ll push an update of the plugin containing a couple of other fixes as well (the reason why you’ve been getting the Created user login field for record at row 2 messages for instance).

• This reply was modified 6 years, 8 months ago by Thomas S.

Hi,

I just pushed a new release that attempts to fix the New User Notification issue you’ve reported.

I’ve also added a section in the FAQ about some typical reasons why it’s possible the notification isn’t being sent or received.

Thanks for bringing the issue to my attention. I’ll have to try and figure out a way to limit the available resources for my own test.

My test .CSV file has 5000 users it and imports without issue, so I _thought_ my estimates were safe. I stand corrected and will work to try and come up with a better way to avoid timeouts.

Hi,

The Error Log message seems pretty indicative, unless you’re suggesting the plugin is not including the information?

Missing ID, user_login or user_email information column

Is it possible that you haven’t got a valid email address column (with the user_email column header to denote it) in your import file?

If you _do_ have one of the 3 fields the error log mentions, would you mind providing me with a way to review your import source file?

Thank you for that analysis!

The fix in 2.7 is a little bit different than what you proposed, but you helped me realize that as I ported from the original, I left a piece of code in my version that shouldn’t have been there (causing the subscription_transaction_id, payment_transaction_id, affiliate_id and payment_gateway fields to get zeroed out accidentally).

I just pushed 2.7 out so it should become available fairly soon.

No worries.

I may not be as responsive over the weekend, sorry.

If max_execution_time is set to 300, that’s 300 seconds (i.e. 5 minutes). That should be plenty!

Could I ask you to enable WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file and then try an import again?

I.e:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Once the import fails/is done, could you link the the wp-content/debug.log file somewhere I so can access it (before you delete the file again)?