Yep, I'm sorry, this is my third post in a week relating to the Locale module, but I'd really appreciate some advice.
I've been trying to configure blocks to appear on certain pages through the standard mechanism of specifying paths, but I've noticed that the language prefix which is being added by the Locale module is being ignored.
For example, with the Japanese language prefix set to 'jp' I end up with paths like:
jp/something/something (where something/something is the path alias of the node).
However, if I set the visiblity of a block to only appear on 'jp/something/something' it isn't shown.
If however, I set the block visiblity to 'something/something' it is displayed on 'jp/something/something'.
The logical conclusion is that the prefix which is added by the Locale module is being ignored when drupal works out which blocks should be displayed on a given page.
Is this the intended behaviour? I'm just a bit concerned that there could be something wrong with my setup. I'm a bit concerned as the behaviour which I'm seeing seems to contradict information which I found on another post.
Perhaps it is intended in order to allow people to change the language prefix while still maintaining the same block visibility settings, but I'm just not sure.
Once again, any advice greatly appreciated,
Richard
Comments
Yes, I think it is the intended behaviour
Yes, I think it is the intended behaviour. You could use PHP for block visibility. If these are "custom" blocks, you could try Language Sections (to allow a single block holding content for multiple languages).
Currently part of the team at https://lastcallmedia.com in a senior Drupal specialist role.