Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
diving deeper into a bug found with commons below, it looks like the message module isn't compatible with locale. Our specific issue is in views, where the rendered message doesn't appear if locale is enabled.
Issue: http://drupal.org/node/1932530#comment-7145288
has anyone else tried locale with message module, and do you see similar issues?
Comment | File | Size | Author |
---|---|---|---|
#8 | recentactivity.jpg | 33.34 KB | m.schwarzenberg |
Comments
Comment #1
japerryThis is a duplicate of: http://drupal.org/node/1782134 we're using the rendered entity function for the entity module.
Comment #2
japerryrealized that what we need to do here is implement a the patch locally in the message module, because Fago doesn't want it in the entity api itself.
Comment #3
hservaes9 CreditAttribution: hservaes9 commentedHello, same problem with locale module enabled and commons 3.1. If you have the same problem, the only solution is to disable locale module. Then, after modifications, reactivate locale module. No other solution for now ? Thanks.
Comment #4
albertosouza CreditAttribution: albertosouza commentedSame problem in commons 3.3 rc 4 and the only way I found was to translate the language und ( none ) from my language
I think we need a fix here
Comment #5
ezra-g CreditAttribution: ezra-g commentedAdding this issue to the 3.4 radar.
Comment #6
Devin Carlson CreditAttribution: Devin Carlson commentedI'm not seeing the same behaviour as has been reported using earlier versions of Commons.
Can someone post the steps to reproduce this using a fresh install of Commons 3.3? :)
Comment #7
slowflyer CreditAttribution: slowflyer commentedI'm currently working on a community updated from 3.2 to 3.3.
All messages are translated to locale languages, except "Commons Posts - Post Created" which has been added to 3.3.
I added translations for different languages to this message as I did with all other messages, but no matter what I do, it still displays the text for undefined language.
Comment #8
m.schwarzenberg CreditAttribution: m.schwarzenberg commentedAlso an issue in Open Atrium which uses message module:
'Can't see nodetitles in recent activity' https://drupal.org/node/2036413#comment-7948655
Comment #9
RoySegall CreditAttribution: RoySegall commentedAltough this is and old issue i managed to reproduce and found how to fix this. You can go to admin/config/system/message/text-copy and copy the current field value to other language.
Comment #10
Zatox CreditAttribution: Zatox commentedhttps://docs.acquia.com/commons/develop/translate
Steps 6 and 7 explain how to translate messages in Commons. Works fine for me with 3.4
No need to use Lingotek translation (steps 1 and 2) by the way. I used the good old locale module with l10n_update and it also works.
In simple, do as #9 says and then
Manualy 'edit' each message to manualy translate them. Image tutorial here: https://drupal.org/comment/7268112#comment-7268112
Comment #11
Thytane CreditAttribution: Thytane commentedWith drupal commons 7.x-3.30, the problem with activity stream is always here.
The solution #10 works perfectly.
Comment #12
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedThis is still happening. There is an issue between locale and the message module
Comment #13
niallmurphy-ie CreditAttribution: niallmurphy-ie commented---
Comment #14
bluegeek9 CreditAttribution: bluegeek9 as a volunteer commented