On a multilingual site with path aliases in a specific language, the following message is displayed when saving a Beanstag that containings a non-default language alias.
The path does not exist

This is caused by: 1. the alias in the url_alias table has a language value equal to the language of the node (site is using content translation module); 2. the call to drupal_lookup_path() does not provide a language, and therefore the default language is used to lookup the alias.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sutharsan created an issue. See original summary.

Sutharsan’s picture

This patch fixes the problem for me.
It needs to be investigated if this also works in other multilingual configurations (a.o. Entity Translation).

Sutharsan’s picture

Status: Active » Needs review
FileSize
750 bytes
1.17 KB

I did not consider all return values of language_url_split_prefix(). This patch does better.

Status: Needs review » Needs work

The last submitted patch, 3: beanstag-multilingual-path-2660212-3.patch, failed testing.

ykyuen’s picture

Great~ thx for your patch. I will take a look and release them in the coming weeks.

ykyuen’s picture

Status: Needs work » Needs review

path applied to dev branch. if no problem, will create a new release. thanks again. =)

ykyuen’s picture

Assigned: Unassigned » ykyuen

The last submitted patch, 2: beanstag-multilingual-path-2660212-2.patch, failed testing.

ykyuen’s picture

it should also works in entity translation.

ykyuen’s picture

Version: 7.x-1.x-dev » 7.x-1.4
Status: Needs review » Closed (fixed)

Committed to 7.x-1.4.