I installed three languages: french, english, german
I defined french as default language
When I created a german node, this one is called .../de/node/xxx
When I created an english node, this one is called.../en/node/yyy
When I created a french node, this one is called .../node/zzz NOT .../fr/node/zzz
Why ? Normal ?

Comments

pepe roni’s picture

pepe roni commented

I would call this a bug! If you don't have specified a path prefix, this behavior is expected, but with path prefix it is definitely not!

AaronCollier’s picture

AaronCollier commented

This is perfectly normal depending on the settings you have chosen. It is part of the Language settings page (admin/settings/language/configure). Choose the option you want there.

You also would want to check your path settings, to see about how it adds prefixes.

phicarre’s picture

phicarre commented

I put "fr" for french nodes !!!

pepe roni’s picture

pepe roni commented

So it is a bug!

With language domains, it seems to work well.

This is caused by the missing documentation:

In admin/settings/language/configure you can select "Path prefix only" or "Path prefix with language fallback". Only with the latter option, the language code of the default language is added to the path, with the first option it is always omitted.

If this works for you, please close this issue.

phicarre’s picture

phicarre commented
Status: Active » Closed (fixed)

OK

AaronCollier’s picture

AaronCollier commented
Status: Closed (fixed) » Fixed

Issues should remain fixed for 2 weeks before closing, so if anyone else has the same issue they can see the fix.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

rcross’s picture

rcross commented
Version: 6.x-1.0-beta3 » 6.x-1.0-beta4
Category: support » bug
Status: Closed (fixed) » Postponed (maintainer needs more info)

i am finding this issue is only partially addressed.

1) going to example.com should (optionally) direct to example.com/default_language_prefix (i.e. example.com/en)

2) it would seem that this functionality should be the same for "Path Prefix Only" and for "Path Prefix with language fallback"

What seems odd is that with my local machine I think this was working properly (w/ D6.3), but when I went to push it to a staging server it didn't work and when I tried to start from from scratch (with D6.4) it isn't working.

AaronCollier’s picture

AaronCollier commented

I think that the point of "Path Prefix with language fallback" would be that there is a language fallback, so that there are nodes without the prefix that exist in the default language. Otherwise, what's the difference between "Path Prefix Only" and "Path Prefix with language fallback"?

jose reyero’s picture

jose reyero commented
Project: Internationalization » Drupal core
Version: 6.x-1.0-beta4 » 6.6
Component: User interface » translation.module
Category: bug » support
Status: Postponed (maintainer needs more info) » Closed (works as designed)

All I see here is some mess with language options.

The main poing, IMHO is that "language fallback" is not compatible with "default language with no prefix". Either you assume that paths with no prefix mean default language, or you find a suitable one (fallback: user, browser, default).

So really, nothing to do here, and anyway this is a Drupal core issue.