Just a quick patch that allows for translated user alert content to be displayed to the proper site based on the global language code setting.

The content type needs Multilingual support 'Enabled, with translation' turned on. Then if you create an alert node in each language of your site, they will each display on their respective sites.

CommentFileSizeAuthor
nodetranslation.patch1.58 KBDanielWashbrook

Comments

kevinquillen’s picture

kevinquillen commented
Assigned: Unassigned » kevinquillen
kevinquillen’s picture

kevinquillen commented
Status: Needs review » Reviewed & tested by the community

Patch looks good. Also noticed and changed the static values 0 and 1 to NODE_PUBLISHED and NODE_NOT_PUBLISHED in those queries.

kevinquillen’s picture

kevinquillen commented
Status: Reviewed & tested by the community » Needs work

If multilingual is not enabled, the language in the query needs to be 'und' or the query will fail otherwise.

kevinquillen’s picture

kevinquillen commented
Version: 7.x-1.9 » 7.x-1.x-dev
Status: Needs work » Fixed

If no content translation is enabled, the query will use LANGUAGE_NONE so it does not fail for non-translated sites. I enabled Locale, Content Translation and Entity Translation (for Field level translation, aka Body field) and was able to create content in a few languages and only see them when requested.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.