[buddypress-trac] [BuddyPress Trac] #6413: xprofile fielddata visibility should be stored in xprofilemeta

[buddypress-trac]

#6413: xprofile fielddata visibility should be stored in xprofilemeta
----------------------------------+---------------------------
 Reporter:  boonebgorges          |       Owner:  boonebgorges
     Type:  defect (bug)          |      Status:  assigned
 Priority:  normal                |   Milestone:  2.5
Component:  Component - XProfile  |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  2nd-opinion           |
----------------------------------+---------------------------

Comment (by boonebgorges):

 @imath - Thanks for the feedback. I share your concerns about the slowness
 of the migration. Though, for what it's worth, *any* batch system we build
 means that there will be at least *some* lag time between BP upgrade and
 full migration. This means, in turn, that BP should always be able to
 handle both old and new data, at least for a version or two (until we can
 be reasonably certain that all installations will have performed the
 migration). I'll work on a patch that covers this backward compatibility.
 In this case, I think we can do it with lazy processing: when loading a
 user's profile, if we detect that the user's visibility settings have not
 yet been migrated as part of the upgrade routine, then we migrate the
 specific user's data before rendering the page. (This is possible in the
 case of profile visibility because this data isn't really used anywhere
 but inside of a `bp_has_profile()` loop. It'd be harder to do this with
 other kinds of data.)

 I've opened #6841 to discuss the more general issue of data migrations and
 update routines. Would like to hear your thoughts there.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6413#comment:7>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac