Hi Gisle.

I'm not sure if you can solve this because solution may depend on how multilingual site is implemented, but I will expose what happens on our website and if you can do anything, it could be great!

Our website is in 3 languages: spanish (main), basque and english.
It's configured to create different nodes for each language, so if spanish version is node/799, basque version (if created inmediately) should be node/800.
Notify emails, display each node as a different "new content". That is correct for me, but spanish link is correct and rest of links go to spanish new.
I give you a real example with title and teaser:
------------------------------------------------------------------------------
Contenido reciente - 2 nuevos contenidos
------------------------------------------------------------------------------
1. Resultados del fin de semana. Artículos by joseba [Published]
[ http://www.donostiarrak.com/es/content/resultados-del-fin-de-semana-20 ]
Otro fin de semana en el que tenemos korrikalaris "por ahí".

----
2. Astebukaerako emaitzak. Artículos by joseba [Published]
[ http://www.donostiarrak.com/es/node/800 ]
Beste asteburu bat non korrikalariak izan ditugun "hor nonbait".
--------------------------------------------------------------------------------
In this case, spanish node is 799 and basque node is 800.
spanish route uses "content" type of URL, that's ok.
basque route uses "node" type of URL. And mixes spanish and bask routes. To be correct should be eu/node/800 instead of es/node/800. Wrong one displays spanish version of node (drupal understands the mix and finally displays es/node/799)

Modules I use for multilingual (all last versions): Internationalization, Multilingual content, Translation redirect, Variable translation, Taxonomy translation, Synchronize translations, Multilingual select, Menu translation, Field translation, Block languages,

What's your opinion about this issue?

Many thanks,

Josean.

CommentFileSizeAuthor
#7 Screen Shot 11-03-14 at 02.55 PM.PNG44.88 KBjosean
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented
Related issues: +#933364: Notify according to User language

Thanks for the report. Notify has never been adapted to work on multilingual sites. There is an open feature request for this (#933364: Notify according to User language ) that is more than three years old.

While full support for a multilingual site is not going to happen soon (unless somebody else does the work), I agree that routing should at least be correct. I'll try to find the time for looking into this, but I am quite busy these days, so it may take a while.

josean’s picture

josean CreditAttribution: josean commented

Thanks Gisle.
Correcting links is enough for me.
And is not urgent, take your time.
Best regards.

  • gisle committed 8841bda on 7.x-1.x 
    #2336961 by gisle: Fixed multilingual notifications.
gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented
Version: 7.x-1.1 » 7.x-1.x-dev
Assigned: Unassigned » gisle
Status: Active » Needs review

This should be fixed in the latest dev snapshot of the 7.x-1.x branch. Please review.

Please note that is now also possible to notify according to user preferred language.

If you've set up a multilingual site, on the Notify Settings page there should also be three radio buttons that allow you to filter notifications about new nodes against the users language setting (may be set by editing the user profile).

  1. The first setting ("All contents") will notify a user about all new contents on the site. If a piece of contents exists in more than one language, all versions will be notified about.
  2. The setting "Contents in the user's preferred language + contents not yet translated" will notify about content in the user's preferred language and also about content that is in some other language if no translation of it exists.
  3. The last setting, "Only contents in the user's preferred language ", will only notify about new contents in the user's preferred language.

Note that new contents that are marked as "language neutral" will always be included in notifications, and that the multilingual settings do not apply to administrators. Administrators will always be notified about all new contents.

josean’s picture

josean CreditAttribution: josean commented

Hi gisle.

Yesterday I updated to version 1.x-dev and today notify has sent this email:
"2. Calculadora de ritmos. Artículos by josean [Published]
[ http://www.donostiarrak.com/content/calculadora-de-ritmos ]"
This path is wrong.
To be correct it needs language info: www.donostiarrak.com/es/content/calculadora-de-ritmos

Can you have a look?
In the meantime I will revert to 1.1 to avoid broken links.

Thanks

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented

How is the path (/es/content/calculadora-de-ritmos) alias generated?

With node paths (e.g. /node/42) it is not recommended to include the language in the path. The language info is not really a part of the path in this case, it is there to allow redirection to the node with the correct language if an alternate version exists. However, having the language as part of the path is only one method to indicate language. Drupal can be configured to use other methods (e.g. language preference set in the browser, or user default language) instead.

Will it be OK if Notify always used the /node/XX path, instead of the path alias?

josean’s picture

josean CreditAttribution: josean commented
FileSize
Screen Shot 11-03-14 at 02.55 PM.PNG44.88 KB

Hi, Gisle.

I start with your second question.

- Yes, for me it's enough to use node path because it's different for each node's language version
For example, I give you a real example in 3 languages. All this 6 links work fine:

node path || alias path

/node/852 || /es/content/resultados-del-fin-de-semana-27
/node/854 || /eu/content/asteburuko-emaitzak-8
/node/857 || /en/content/weekend-results-0

- I don't now exactly how alias path is generated. It looks like depending in nodes title, drupal generates in our example "resultados-del-fin-de-semana-27". To refer to this node, by default it uses /content/.
in /admin/config/search/path/patterns I have default values for URL aliases:
Default path pattern = content/[node:title]
I also give you a screenshot

Best regards,

Josean

  • gisle committed 9f5ae85 on 7.x-1.x 
    #2336961 by gisle: Fixed multilingual notifications.
gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented

I've pushed another attempt to fix this to the latest dev snapshot of the 7.x-1.x branch.

Please review.

josean’s picture

josean CreditAttribution: josean commented

Hi Gisle.

I have installed this new dev version (5-nov) and tested only in admin environment.
It works as expected.
Same article in 3 languages (they are 3 nodes), sends 3 different paths, all of them correct.
For example: ...com/node/900 , ...com/node/901 , ...com/node/902

I leave this new version installed to have a real test in some days.
I hope to give you definitive feedback in some days.

Many thanks,

Josean

josean’s picture

josean CreditAttribution: josean commented

Hi Gisle.

After some days and some tests, I can tell you that last dev version works perfect.
For me, this issue will be closed.

Thanks for your efforts.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented
Version: 7.x-1.x-dev » 7.x-1.2
Status: Needs review » Fixed

This is now fixed in 7.x-1.2.

Status: Fixed » Closed (fixed)

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