Support » Plugin: Import Members from CSV for Paid Memberships Pro » Billing_ fields not imported into order

  • Resolved Bill Stoltz

    (@billstotlz)


    Is there a reason why all the billing_street, billing_city, billing_state, etc are not imported into the order?

    It looks like these fields are excluded for some reason.

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

    (@eighty20results)

    Hi,

    The billing_* fields aren’t actually Paid Memberships Pro fields (most likely, they’re WooCommerce fields and IIRC have fairly different field names than what they appear to have in the HTML).

    The PMPro billing information fields have pmpro_b as a prefix. They are (IIRC):

    pmpro_bfirstname
    pmpro_blastname
    pmpro_baddress1
    pmpro_baddress2
    pmpro_bcity
    pmpro_bstate
    pmpro_bzipcode
    pmpro_bcountry
    pmpro_bphone

    sorry, probably a little confusing question.
    Yes, I use the pmpro_b prefix for the billing information. Looks like it sets the user_meta stuff just fine.

    However, there are also fields in the MemberOrder. They are billing information. I think they get sent when you use a gateway to pay, like paypal.

    However, when you import a record and you specify the pmpro_b fields, it does not update any of the billing information in the order. So, when you go back and look at the orders created, they billing information is blank.

    Now, I created an pmp_im_post_member_import action to go find the last MemberOrder by SubscriptionTransactionID and then update the billing fields of the order by the pmpro_b fields of the user.

    But this would not be needed if this was done when the order is created.

    Do you think it makes sense to see if the pmpro_b fields are provided and if so, update the billing fields of the order?

    Thanks,
    bill

    Plugin Author Thomas S

    (@eighty20results)

    Hi Bill,

    Do you think it makes sense to see if the pmpro_b fields are provided and if so, update the billing fields of the order?

    I think it makes sense to see if the data exists for the user and include it in the order if it does (since the pmpro_b data should be present in the DB before the order creation logic runs anyway).

    Thank you for the suggestion! (being implemented now and should be available in v2.30)

    Good point. The data will either exist for the user based on the import or if it was there from another transaction.

    Great thanks for adding this.
    Bill

    Plugin Author Thomas S

    (@eighty20results)

    Should now populate the Order billing information if the pmpro_b* column data exist in the import file for a row (as of v2.30)

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Billing_ fields not imported into order’ is closed to new replies.