[buddypress-trac] [BuddyPress] #1332: Caching issues with profile data when using a persistent cache

buddypress-trac at lists.automattic.com buddypress-trac at lists.automattic.com
Mon Nov 9 13:46:52 UTC 2009

#1332: Caching issues with profile data when using a persistent cache
Reporter:  swinton                   |       Owner:                
    Type:  defect                    |      Status:  new           
Priority:  major                     |   Milestone:  Future Release
Keywords:  xprofile,cache,memcached  |  
 I've noticed some issues with cached profile data when using a persistent
 cache such as memcached.

 The cached profile data isn't expired when new profile fields are added or
 when profile data is changed.

 To reproduce:

 * Configure WPMU/BP to use a persistent cache, such as memcached (e.g.
 install this plugin under /wp-content ->
 and then run a memcached server)
 * Load a member's profile page, and their edit profile page (so that their
 profile data is stored by memcached)
 * Add a new profile field, and reload the edit profile page (the new
 profile field isn't shown)
 * Update an existing profile field, and save the data (the new profile
 field data isn't shown)

 The problem is that the profile data cache isn't being expired at the
 appropriate times, e.g. when a new profile field is added, when profile
 data changes etc.

 This can be worked around using a plugin, to delete the cache at the
 appropriate times, using the provided BP hooks (example attached).

Ticket URL: <http://trac.buddypress.org/ticket/1332>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list