As D6 is getting really close and we all try to test "everyting" I stumbled into an "old friend". This problem started up like a bug/race between the globalredirect and the i18n module. In D6 that part of i18n is moved into the D6 core, so all you need to test/trigger it, is a D6 installation and the globalredirect module. No I'm not so sure anymore, if it is a "D6 problem" and if it should be moved to D6 issues or if it still is a isolated globalredirect bug?
I just want to be sure that the path-handling in D6 is as robust as possible. Is jose also the maintainer for the "core part" of i18n? "nicholasThompson" write that he is fully booked and don't have the time to look into the issue, and that's perfectly OK, but I want to get the i18n people's attention, and everyone else involved in making international sites, and maybe there is an other way to solve it.
--
Stein Magne
http://smbjorklund.no
Comments
Hi Stein, I'll look more in
Hi Stein,
I'll look more in depth into the D5 issues.
But about D6, yeah, you should create a separate issue as all this is handled in core itself (the path handling is much nicer than in i18n for D5 though) so I guess it won't be that difficult fo fix. Also no code has been copied from i18n, it's a clean implementation what you can see in D6 core.
However while on D5 it was a compatibility issue between two contrib modules, if it persists in D6 it should be labelled better as a module's bug, as it is an issue with Drupal core.
I'm not a maintainer for Drupal core, Gabor is the maintainer for that part.
Issue created
Hi Jose
Thanx for looking into this issue. I have reg. this issue against D6 http://drupal.org/node/216271
--
Stein Magne
http://smbjorklund.com
--
Stein Magne
http://smbjorklund.com