• hastibe

    (@hastibe)


    I’ve selected several fields in the “Additional wp_usermeta Table Fields (For Developers)” section of WP Fusion Lite’s Contact Fields page, which have been added by the Ultimate Member plugin (e.g. phone_number, full_name, list) to push to fields in Mailchimp when a new user registers, but the logs show that they aren’t being pushed (only the core contact fields at the top of the Contact Fields page are listed as being pushed to Mailchimp). Looking at the logs, it is as if the fields in the “Additional wp_usermeta Table Fields” aren’t checked at all, as they don’t appear anywhere in the logs.

    I’ve tried with the “Push All” option on the Advanced page checked, but that hasn’t resulted in any change. I also have verified that the additional metadata fields for the user are populated via a metadata viewer plugin. Is there something I am missing or is there a compatibility issue?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter hastibe

    (@hastibe)

    I’ve also tried registering a new user with “Activate API Queue” unchecked with no change. The Ultimate Member fields appear and can be selected and mapped to Mailchimp fields on the Contact Fields page of WP Fusion, and then they just aren’t pushed to Mailchimp (even though I do have “Push” to “Sync profile updates and custom field changes to the user’s contact record in Mailchimp” checked on the General Settings page of WP Fusion) when a new user registers (via the Ultimate Member registration form, of course). Very confused, since Ultimate Member is listed as a compatible plugin and its fields do appear in WP Fusion.

    Plugin Author Jack Arturo

    (@verygoodplugins)

    Hey @hastibe 🙂

    WP Fusion Lite only officially supports the WordPress “core” fields like first_name, user_email, user_login, etc. With other profile plugins like Ultimate Member they’ll sometimes work, but it’s hit or miss.

    Generally with the “additional fields”, if they’re enabled they will sync at at the time of registration (or profile update) if enabled field IDs are present in the POST’ed user data that’s sent with the rest of the registration form.

    For example, for phone number, you’d need to make sure you have an <input type="text" name="phone_number"/> present on the form alongside the email and other registration data.

    Off the top of my head, Ultimate Member was a tricky integration because the field names are unique to each form ID… so instead of name="phone_number" you’d see something like, name="um_1_04". There was also some complexity with form field validation, forms requiring approval, AJAX (i.e. background submitting) forms… and a few other things. It took about four years to get right 😅

    Unlike the WP Fusion Lite, the full version of WP Fusion does have official compatibility with Ultimate Member (https://wpfusion.com/documentation/membership/ultimate-member/ ), and about 150+ other plugins. Basically we’ve gone through the suffering for you to make sure that field detection and sync is automatic no matter what type of form, field, or how your registration flow is set up.

    So it’s not that WP Fusion Lite is specifically incompatible with Ultimate Member, it just doesn’t have any special treatment for Ultimate Member. The full/paid WP Fusion has (checking….) an extra 848 lines of code specifically to handle all that UM wierdness 🙂

    Best
    Jack

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.