Skip to:

Opened 15 years ago

Closed 10 years ago

#769 closed enhancement (duplicate)

Update idea for Activity Streams

Reported by: johnjamesjacoby's profile johnjamesjacoby Owned by:
Milestone: Priority: major
Severity: normal Version:
Component: Core Keywords:


Currently, the text for the activity stream is written directly into the database, leaving it uneditable by the end user, and putting repeating text into something that can be standardized.

I propose a new version of streams to adopt a version of an open stream standard, that is based on the initiating object, the action, the receiving object, the result, and the extra. From my brief investigation into this, there are open stream initiatives, but I'm not sure of any standards being adopted yet. Maybe we can start one?

John | added | Andy | as a friend

Andy | posted | BuddyPress 1.0.1 Released | in | BuddyPress Development

Burt | joined the group | Hairless Dogs

This allows translation of the individual pieces of text, and allows plugin authors to modify their plugins' stream text without requiring a conversion of the streams in the database. Currently, when using a multilanguage BuddyPress setup, the activity feed is saved in the language mode that the site is currently in when that language is performed, and cannot be translated since the text is saved in the DB rather than built through an array of some kind.

It looks like the database may have been designed with this type of functionality in mind, since all of the pieces of the action have their own distinct column in the table. Maybe this would be as easy as a sprintf on the pieces, and having the stream text in an array?

Change History (6)

#1 @dinhluong
15 years ago

I think this would fix something else I've noticed - that stream items don't get changed when things are updated, like when a user changes their display name or a post is retitled.

#2 @(none)
15 years ago

  • Milestone Activity Streams 1.1 deleted

Milestone Activity Streams 1.1 deleted

#3 @cnorris23
14 years ago

  • Component set to Core
  • Milestone set to 1.3

#4 @boonebgorges
14 years ago

  • Milestone changed from 1.3 to 1.4

This would be a dream come true, but will have to get bumped to the next big version at least.

#5 @DJPaul
13 years ago

  • Milestone changed from 1.6 to Future Release
  • Severity set to normal

#6 @boonebgorges
10 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicates #3856. Fixed in BP 2.0. See r8125.

Note: See TracTickets for help on using tickets.