Skip to:

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#3814 closed enhancement (fixed)

Collect activity meta at the beginning of an activity loop, using new cache functions

Reported by: boonebgorges's profile boonebgorges Owned by: boonebgorges's profile boonebgorges
Milestone: 1.6 Priority: normal
Severity: normal Version:
Component: Activity Keywords:


See #3799

Apply to the activity component.

This is going to be tricky, because of the way the activity component currently constructs its activity meta cache keys. They are of the format

'bp_activity_meta_' . $meta_key . '_' . $activity_id

rather than

'bp_activity_meta_' . $activity_id . '_' . $meta_key

The latter method is how bp_update_meta_cache() expects the keys to be constructed, and is the way that it's done in other components. That will mean doing some backpat work, probably just checking the legacy cache key in bp_activity_get_meta().

Change History (4)

#1 @johnjamesjacoby
13 years ago

  • Owner set to boonebgorges
  • Status changed from new to assigned

#2 @boonebgorges
13 years ago

  • Milestone changed from Awaiting Review to 1.6

#3 @boonebgorges
13 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [5505]) Collect and cache activity meta at the beginning of the activity loop, for quicker lookups. Fixes #3814

#4 @boonebgorges
13 years ago

I ended up just changing the way that the activity meta functions cache their values. This shouldn't affect anyone, unless for some reason they were accessing the cache directly.

I'll write up a post on bpdevel about the recent cache changes, and will cover this issue.

Note: See TracTickets for help on using tickets.