Skip to:

Opened 13 years ago

Closed 13 years ago

#3063 closed enhancement (wontfix)

All activity stream messages should use main site's language

Reported by: settle's profile settle Owned by:
Milestone: 1.5 Priority: normal
Severity: Version: 1.2.6
Component: Activity Keywords: close


We use WP Multisite and BP and we allow users to choose their blog language in blog settings.

And everything what happens in their blogs gets synchronised with "wall" in default site (

Default language in the main page is lithuanian, but few blogs still use english. When a new comment or new post appears in that blogs it gets synchronised with main page, but strings like "commented on the blog post" stay not translated.

I think that main page "wall" should always use its own language, although some blogs use different language.

I'm sure, it is difficult to understand me, so I will attach image. I hope it will help to understand.

Attachments (1)

screenshot2.png (33.0 KB) - added by settle 13 years ago.

Download all attachments as: .zip

Change History (11)

13 years ago

#1 @DJPaul
13 years ago

  • Milestone changed from Awaiting Review to 1.3
  • Resolution set to invalid
  • Status changed from new to closed

This content in the activity stream is written once; that is, it is stored in the database by the site that generates the activity. Wherever it is read out, it is not re-generated. This is causing the display that you are seeing.

#2 @settle
13 years ago

No, I have just checked, it doesn't look like it is written once.

For example:
We have multisite called, which uses lithuanian language.
And we have a blog, which uses lithuanian language, too. If somebody writes a comment in my blog, a new message in main page activity stream appears and is written in lithuanian.

Now, I go to my blog settings and change my language into english, and write a new comment in some post. And I see an english message in the main page activity stream, not lithuanian as before.

As I said, it depends on currently set blog language.

And I still think that all activity stream messages should rely on main page language, not individual blogs in that multisite.

Last edited 13 years ago by settle (previous) (diff)

#3 @settle
13 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#4 @settle
13 years ago

And maybe you understood me incorrectly. I am not talking about regeneration of old activity messages. I am talking only about messages which are going to be posted in the future.

#5 @DJPaul
13 years ago

Changing the language for a site will cause it to load a different localisation file. The actual text in the activity stream therefore, as you say, depends on which site the "add this to activity stream" action is invoked and that site's language setting.

This is why you are finding differences in the activity stream. This is working as it should. Asking for all activity stream messages to use the main site's language is an enhancement request and not a defect.

#6 @settle
13 years ago

  • Summary changed from Strings are not translated if they are related with blog which uses other language to All activity stream messages should use main site's language
  • Type changed from defect to enhancement

#7 @settle
13 years ago

Ok, I agree, it is an enhancement.
I think you should create a possibility in BP settings to choose which language to use in the activity stream: either different blog's languages (currently) or main page's language (my suggestion).

#8 @DJPaul
13 years ago

  • Milestone changed from 1.3 to Awaiting Review

#9 @cnorris23
13 years ago

  • Keywords close added

This seems like an extreme edge case, plus there are enough filters/hooks that some sort of crafty solution could be had. I don't see any reason to over-complicate core with this. Suggest closing... again.

#10 @DJPaul
13 years ago

  • Milestone changed from Awaiting Review to 1.3
  • Resolution set to wontfix
  • Status changed from reopened to closed

Closing as agreeing with cnorris23's comments above. There are filters in place if a plugin wants to change the text on the way in. It's an edge case for core.

Note: See TracTickets for help on using tickets.