Some time ago, I created a page, gave it a custom path alias 'chata'. Locale was off, so no language was specified.

Today I switched locale on for the first time.

I edited that page, changed the language (because it is in Slovak), saved.

From then on I could not access my page at /chata. I tried editing the page and saving it (the path was there in its field as it should be), but I was always getting an error message. When listing in views, I saw that page had only the /node/nid address, while other pages (without adjusted language) successfuly used their paths.

I then edited the page again and changed the language to 'English' (default language on that site). Now it works.

So the bug is that I cannot set a path alias on a page that has a different language than default/English.

Comments

saml’s picture

saml commented

I have experienced the same problem. I have so far localized my problem to the i18n synchronization module. When either inactivating the module, or inactivating all synchronizations settings for the relevant content type, the problem was gone. Does this help for you too?

I'm investigating this further.

vacilando’s picture

vacilando commented

@saml -- thanks for the idea but no, I don't have the i18nsync module switched on at all.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (works as designed)

Even though locale.module was disabled, the node alias was automatically given the default language on your site (English perhaps?). You changed the language on the node, but the alias language didn't change, so you couldn't access it with the changed language. Try editing the alias on the admin/build/path page.

vacilando’s picture

vacilando commented
Version: 6.13 » 6.15
Priority: Normal » Critical
Status: Closed (works as designed) » Active

Dave, thanks for coming back on this. But there still is a problem. I did not explain it very well above. Forget the locale module switching on and off. Take this scenario which I've just tested in a fully patched current Drupal website:

Create a page. Leave language selector on default = English. Give it an alias, save. The page is available under the alias, OK.

Now edit the page. Change the language. Save. Drupal tries to go to the alias, but returns "Page not found".

When I look at /admin/build/path I can see that the alias points to the correct node/XXXXX and the language is the new language.

Interestingly - and I may not have noticed this before, there was an error msg like this:
user warning: Duplicate entry 'node/XXXXX-' for key 2 query: INSERT INTO path_redirect (source, redirect, query, fragment, language, type, last_used) VALUES ('node/XXXXX', 'MYALIAS', '', '', '', 301, 1265453193) in /MYPATH/includes/common.inc on line 3467.

Now edit the page again. Change language to the default one. Save. Page works again under the alias.

Let me know if anything remains unclear or need more info/other test.

mpegyna’s picture

mpegyna commented

What language have you set for your aliases in pathauto config at administer>site building>url aliases?

vacilando’s picture

vacilando commented

(I am not using the 'pathauto' module.)

As for what language appears in that location -- that's /admin/build/path and I've described it in my report #4 above.

drugget’s picture

drugget commented

Dave Reid, thanks a lot.
admin/build/path - that works!

dpearcefl’s picture

dpearcefl commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

is this still an active issue?

dpearcefl’s picture

dpearcefl commented
Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active
vacilando’s picture

vacilando commented

AFAIK, yes. Try the scenario described in detail in #4 above.

dpearcefl’s picture

dpearcefl commented

Do I can try to duplicate the issue, do you know if it exists in Drupal 6.22?

vacilando’s picture

vacilando commented
Version: 6.15 » 6.22

Yes, I've just tested it and I confirm it still does not work in Drupal 6.22.

Simple/clarified steps to reproduce the bug:

Create a page. Leave language selector on default = English. Give it an
alias, save. The page is available under the alias, OK.

Now edit the page. Change the language. Save. Go to the the URL you have created above (with the alias). You will get "Page not found".

dgastudio’s picture

dgastudio commented

same here

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.