Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Thomas S

    (@eighty20results)

    Hi,

    Thank you for using my plugin!

    The file you linked to is not available (my plugin will clean up after itself eventually).

    However, I feel fairly confident there’s a formatting error in either your dates or there’s something unexpected in the membership_id column for the problem you’re describing to be present.

    Thread Starter Pankaj Mohale

    (@pankajmohale)

    Hi,

    My csv file link is
    https://nrea.org.au/newnrea/wp-content/uploads/e20r_imports/UsersNewdataMREA.csv

    Can you please check it once and give the solution for this.

    Plugin Author Thomas S

    (@eighty20results)

    Hi,

    Just tested with your example .CSV file and although there was a warning issued for the import data by my plugin, the two users were imported with the membership info included (they’ll show up as expired – aka “Old Members” list on the PMPro Members List page).

    The “role” value you supplied didn’t get imported because WordPress doesn’t recognize “Subscriber” as a valid role name when the plugin attempts to set/update the user info (the correct value for the role should be subscriber aka the ‘slug’ for the role).

    The warning received in the import error log – https://example.com/wp-content/uploads/pmp_im_errors.log – has to do with the fact that one of your records (‘Ruoqi Zhao’) had recurring billing data configured/included _and_ had the membership_enddate set.

    Warning: You have an end date AND a recurring billing configuration (the membership_enddate, membership_billing_amount, membership_cycle_number and membership_cycle_period columns are not empty) user (ID: 12). Could result in an incorrectly configured membership for this user

    Plugin Author Thomas S

    (@eighty20results)

    I’m going to close this topic as resolved since it appears the data is being imported in accordance with the content of the import file.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Membership data not updated correctly’ is closed to new replies.