emilyb6116

That worked. Thank you! I had to end up changing update_post_meta to add_post_meta to get it to keep the existing permissions and add the additional one.

Great, thank you!

Will this add the specified role to whatever is there, or replace the role all together if there is one already in place?

Awesome. Thanks so much for the work you’ve done on this. I’ll definitely test and report back.

I did a quick test removing the code that is limiting my pull requests and confirmed that it is the same issue. The value when removed from SF does not delete on WP when a pull occurs. I have not tried to run this the other way as my setup is designed to go just from SF to WP.
I think that does give me now two issues, sync meta values not removing, and also not being able to isolate and only sync the contacts that have only had modifications to the custom field.

Looks like this pull fixed everything on my end! I really appreciate the help on this.

Agreed about the friendly names. I left the values alone but changed the API name for the picklist to match the role slugs in WP. Seemed to do the trick.

Thanks to both of you for the support!

Ok, I did some more testing and I think I’m closer!

I have successfully passed the value of the multi-select picklist to WordPress, but now it won’t show in the checkbox list in the backend of WP user edit, or in the Users list in the Roles column (just says none for that user). However! It does show when I filter to users with that specific role. It will then correctly list the user that was updated with the new role.

I’m mapping it to wp_capabilities, but should I also be mapping to wp_user_level?
The meta_value for wp_capabilities is different in the database between my test user with the mapped role and another user with the same role but added in WP admin.

Thanks for the clarification!