Undefined offset when updating the last_activity

[imath]

I think it's linked to r8320

Seems the cached value should be the entire array and not only the value of the user_id index in BP_Core_User::get_last_activity()

[boonebgorges]

The 'bp_last_activity' cache is already keyed by user ID. Storing the whole $retval array doesn't seem right. This needs further investigation and unit tests.

[imath]

Well, another way is to not try to update the activity using an index that is not set. See 5590.02.diff

[boonebgorges]

Are we sure this needs to be fixed in 2.0.1? If it was caused by r8320, it's not in the 2.0 branch.

Well, another way is to not try to update the activity using an index that is not set. See 5590.02.diff

This change would definitely need unit tests. I'd have to look closer to see how it would affect existing content, fetching for multiple users, etc.

[imath]

Oops, sorry i was wrong, i think i need a good night of sleep.

[johnjamesjacoby]

See #5597 for more details on this issue, closed a duplicate of this one since there's discussion here already.

Also see r8326 (committed to trunk) which tests subsequent calls to BP_Core_User::get_last_activity() to compare cached results to original non-cached results.

[johnjamesjacoby]

In 8327:

Add unit test for comparing subsequent calls to BP_Core_User::get_last_activity() to compare cached results to uncached results. See #5590, #5597, to test logic introduced in r8047. (2.0 branch)

[boonebgorges]

In 8332:

Overhaul caching for user last_activity values

The last_activity methods in the BP_Core_User class were originally designed
without persistent caching in mind. In r8047, some minimal caching support was
introduced, but it was tacked on and incomplete. In particular, it depended
on an inconsistent structure of return values from the last_activity methods.
See #5128 for more background.

This changeset introduces a number of changes that make last_activity methods
perform more consistently, as well as full support for object caching.

• BP_Core_User::get_last_activity() always returns a multidimensional array of last_activity arrays, keyed by user_id. This remains true even when last_activity data is being fetched only for a single user.
• last_activity data is stored in the bp_last_activity cache bucket without the user-id-keyed wrapper.
• BP_Core_User::get_last_activity() now uses the same caching technique as other BuddyPress and WordPress queries: detect which requested items are not yet in the cache, prime the cache for those items, and then fetch all requested values directly from the cache to build a return value.

Fixes #5590

Props imath, johnjamesjacoby for initial patches