Plugin Author
Thomas S
(@eighty20results)
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?
Thread Starter
dexr
(@dexr)
Thanks for your quick reply Thomas.
Today I see there were new updates for both the native Import Users from CSV with meta (1.11.3.1) and PMPro Import Users from CSV (3.3) so I have upgraded both.
I re-imported via Memberships > Import Members in a subsite and see error report:
BEGIN 2018-03-20 07:34:51
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
BEGIN 2018-03-20 07:34:52
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
BEGIN 2018-03-20 07:34:52
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
BEGIN 2018-03-20 07:34:52
[Line 1] Created user login field for record at row 2
[Line 2] Created user login field for record at row 3
[Line 3] Created user login field for record at row 4
I’m guessing this is because I was in a subsite Dashboard when I did the import. When I delete the users and go back to the master site, the same file imports clean ‘Member import was successful.’
However, in both cases it still does not import the memberships and the users show in the subsite as ‘Membership Level = None’
Perhaps this is because at the master site level I have not set up any membership levels. On the subsite I have set up membership levels 1-6 and in the import data I have nominated levels 1, 2 & 3.
Here is the import CSV file: https://www.dropbox.com/s/0070468g5cu8lgk/import_sample_fix.csv?dl=0
Any further clues please?
thanks again
Dex
Plugin Author
Thomas S
(@eighty20results)
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 8 years, 2 months ago by
Thomas S.
Plugin Author
Thomas S
(@eighty20results)
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!
Thread Starter
dexr
(@dexr)
Thanks Thomas. Here are my steps today:
1. Updgrade the plugin to v2.10
2. Go to the subsite dashboard where the member levels 1 through 6 are set up
3. Fix the date formats in the input file to 2018-01-01 08:00:00,2018-06-30 23:59:00
4. Leave the membership_id as 1, 2 and 3 for the three data rows (all valid)
5. Import using Memberships > Import Members
==> Data format error(s) detected during the import. Some records may not have been imported!
Error log:
BEGIN 2018-03-21 04:38:23
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
BEGIN 2018-03-21 04:38:24
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
BEGIN 2018-03-21 04:38:24
[Line 1] The membership ID column in the import .CSV file must exist, contain a number (the membership level ID) and be an existing membership level ID. (Skipped!)
However, the three users have been imported, they do show up on the member list, they do have the correct membership level attached to them and orders were created as required. So case closed.
What I will do now is abandon this ‘sample data’ file and build a real import file from my member data, using membership levels as they are set up. I will see how that fares.
Thomas thanks again for your help and for your extremely useful plugin.
Plugin Author
Thomas S
(@eighty20results)
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.
