[buddypress-trac] [BuddyPress Trac] #6344: Visibility levels: naming

buddypress-trac noreply at wordpress.org
Fri Apr 3 11:50:51 UTC 2015

#6344: Visibility levels: naming
 Reporter:  landwire      |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  API           |     Version:
 Severity:  normal        |  Resolution:  wontfix
 Keywords:                |

Comment (by boonebgorges):

 > Normal buddypress installs should not be affected with a name/key change
 like that or would they?

 They would. The 'id' is what we store in usermeta to identify a user's
 settings. So we'd have to swap it out for every member on the site.
 Because the data is in a serialized array (for some annoying historical
 reasons), we would have to do it in PHP rather than pure MySQL. This means
 that it'll be a fairly heavy operation on large sites, meaning that we'd
 have to have an asynchronous script for the migration. You see how this
 gets complicated fast :)

 Then yes, there would be a problem with plugins expecting the 'adminsonly'
 visibility field. When necessary, we will make changes like this, and
 attempt to inform developers in the way you've suggested. But we generally
 prefer to remain backward-compatible, unless breaking changes cannot be
 avoided. The current case is one where the implementation is perhaps a
 little unclear and annoying, but there's no real bug, so it's definitely
 not worth breaking existing plugins.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6344#comment:4>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list