|
Jonas Brand
|
June 26, 2015 at 4:48 am
Hi,
we’re using EventEspresso on different subsites of a WordPress multisite which works fine. Now I see in the code of the WP User Integration add-on that you’re saving the attendee ID of a user in the user meta. The problem here is that the user meta is always network-wide (saved in wp_user_meta) and in our case the attendees are saved in the subsite-specific tables (e.g. wp_27_esp_attendee_meta and wp_27_posts). Which means that on subsite 27 it works fine, but on subsite 28 the attendee ID that is saved in the user meta will not exist, because there won’t be a fitting entry in wp_28_esp_attendee_meta and wp_28_posts or it might even refer to a different attendee that has the same attendee ID. So the add-on will be totally unusable on a multisite installation. It would make more sense to save the user id in the (post) meta of an attendee and not the other way around. Probably it’s now too late to change that, but I wanted to make you at least aware of that issue.
Regards
Jonas
|
|
Jonas Brand
|
June 26, 2015 at 4:50 am
I’m talking about the recently released WP User Integration add-on for EE4 to be clear… forgot to mention that.
Regards
Jonas
|
|
Darren Ethier
|
June 26, 2015 at 8:32 am
Hi Jonas,
I wasn’t really thinking (obviously) of multisite support when building the addon. Thanks for taking the time to write your post. We’ve got a ticket created to fix this. What I’ll likely be doing is replacing all instances of {x}_user_meta() functions with {x}_user_option() functions which allow for site specific user meta.
|
|
Josh
|
July 30, 2015 at 1:34 pm
Update: The future release of the WP User Integration add-on is now available. Version 2.0.1 includes a change where it now uses the {x}_user_option() functions.
|
