Removing URL Prefix

Remove the line you added to your settings.php file

For me, Localizer is not creating any problems with other modules, but the problem is that v.3 cannot preserve my existing URLs.
A bilingual site I am supporting is powered by Drupal 5.7 + Localizer 1.10, and I have there some pages with language-symmetrical URLs, such as "lang1/about" and "lang2/about", with path aliases configured manually for the two nodes in two languages. If I upgrade to Localizer v.3, I would not be able to keep these URLs, because now the language prefix is added automatically, and I cannot change both "lang2/about" and "lang2/about" to just "about" since the system does not allow me to have identical aliases for two nodes.
So, now I'm still using Localizer v.1.10 and am not going to change it till I'm able to preserve symmetrical URLs. Neither Localizer v.3 nor i18n can do it under Drupal 5. However, it should not be a problem for Drupal 6. D6 + i18n already allow language-symmetrical URLs.

That worked.
Should have read the install directions again first.
Thank you!

I studied Drupal core a bit more.
There is only a way to do this : patching the core path module.

With D6 already available I don't know if it has a sense to do all this work.

Hi Roberto,

> With D6 already available I don't know if it has a sense to do all this work.

I'm in the same boat (existing content with language-symmetrical paths and url aliases that already contain the language). From what I read here, I think I will skip localizer 3 and stay with 1.10 until I upgrade the entire site to Drupal 6. Since Localizer 1.10 and Localizer 3 are so different, could you perhaps leave 1.10 available for download as one of the official versions?

So I think you are right and there is no sense to patch the D5 core for Localizer 3. Maybe this time would be better spent in upgrading Localizer to Drupal6.

Yes localizer 3 is very different form previous versions because I tried to create a version
more compatible with Drupal 6 for future upgrades.

Other big drawbacks of the previous localizer version were :
- cache compatibility
- SE compatibility

Added again the download for release 1.10.

Thanks

Roberto

> Other big drawbacks of the previous localizer version were :
> - cache compatibility
> - SE compatibility

But this should not be a problem since all my paths are normalized (all URL Aliases already include the language code), right?

> But this should not be a problem since all my paths are normalized (all URL Aliases already include the language code), right?
Right

is i possible to reinstall the version 1 instead of 3.3 in a safe way

because i lost my pagerank on google, and this is causing me problems

Hello.

I have just uploaded on CVS some improvements and fixes.
The language prefix is automatically added only for non-node pages.

For your contents you can decide if localizer should add the language prefix
or not.
The language is detected not only from path but also from node language.
This should make localizer more compatible with previous versions and
permits the upgrade, because the old paths will remain untouched.

Two options has been added in localizer settings under "Content settings" :
- Automatically prefix language to content
- Prefix language prefix on new translations
So, if you created your home page and are going to create the Italian translation,
localizer will set the default path to it/home (you can change it, of course)

The fixes include :
- Better home page url management
- SQL fixes submitted by deining
- User Localizer settings form

I would be glad if someone could help me testing these features.
Thanks

Roberto

--
http://www.speedtech.it

the sad thing

is that i could not wait..after advertiser ..rejected by my lost pagerank
so i moved to i18 module

i will keep u informed if i move back

many thanks

Hello,

I have the same problem, url's containing (from v1.10) the language. So I'll test, quickly, the patch. Where can I download it?

Situation:
- site upgraded from 5.2 to 5.7
- deleted the localizer 1.10 stuff
- upgraded to 3.3

Can I use the patch in this situation? Where can I download it?

TIA,
Fossie

It is the 5.x-3.x-dev version (as of March 25 2008) on the Localizer project page. http://drupal.org/project/localizer

It has a setting in the Admin > Localizer area that lets you choose not to append the prefix to content created. I can verify that it is working on my site. This should help many people.

Note that the prefix in the URL is still present for language switching itself, so the "problems with other modules" will not necessarily go away. However, this is also the way Drupal 6 works, so somewhere there has to be some give and take I guess. I still want to get my Gallery (G2) operational again though.

Anyway, thanks Roberto for the effort on the URL prefix!

It's still not working as I expected, but indead I can disable the URL prefix. How can I use version 1.10 in combination with drupal 5.7, do I have to patch the replacement core files (pre-patched for drupal 5.2/3 5.5) ?

from #10:

> The fixes include :
> - Better home page url management
> - SQL fixes submitted by deining

Are you refering to:
http://drupal.org/node/236182
If so, this issue is still unresolved and my submitted fix has not been committed to CVS yet.

> I would be glad if someone could help me testing these features.

I just installed the latest CVS checkout and disabled the URL prefixes alltogether (I didn't like them from the very beginning). At the first glance, everything seem to work fine, however I haven't tested things intensively.

Thanks Roberto for your efforts!

Regards, Andreas

>Are you refering to:
>http://drupal.org/node/236182
>If so, this issue is still unresolved and my submitted fix has not been committed to CVS yet.

Sorry, my fault.
It should be committed now.

Thanks

Roberto

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