As reported in #1806678: Multilingual site, paths not prefixed with language and #1836300: Multilingual site has language duplicated in the path, though I suspect the latter may be unrelated. Let's keep it in this issue.

Basically, when path prefixing is enabled, linking to a node with a path which already has a prefix is causing the prefix to double up: for example, "ja/node/123" becomes "ja/ja/node/123".

I think I have found a fix, and by the time you read this, a new release should be available which hopefully fixes this problem. I'd appreciate it if those who were affected by this bug could report in this issue as to whether the 7.x-2.7 release solves the problem.

Comments

canrull’s picture

I opened #1836300: Multilingual site has language duplicated in the path and I have just installed 7.x-2.10: it solves my bug!
Thanks indeed.

Garrett Albright’s picture

Status: Active » Fixed

Okay, thanks for your feedback. With a lack of any new reports of problems on this, I'm going to go ahead and close this.

Status: Fixed » Closed (fixed)

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

funkytraffic’s picture

Status: Closed (fixed) » Active

I have a multilingual site accessable by http://www.site.com and http://site.com with Pathologic 7.x-2.10 and Secure Pages 7.x-1.0-beta1 installed

I am using Processed URL format with "Path relative to server root (/foo/bar)" with both http://www.site.com and http://site.com as base path for the site.

Only if the link in the text field is http://www.site.com/en/article/some pathauto will return a double path prefix.

Garrett Albright’s picture

Did you mean "Pathologic" instead of "Pathauto?"

Is this happening on all paths, or just paths to files?

funkytraffic’s picture

Of course I meant "pathologic", excuse me.

Garrett Albright’s picture

Is this happening on all paths, or just paths to files?

Do you think you could give the latest dev release a try? It has some improvements which may fix the problems for your situation.

funkytraffic’s picture

This bug appeared on all paths.

The dev seems to correct the bug in my case.

hass’s picture

DEV does not output the aliases. #1885490: Paths not converted to aliases

Garrett Albright’s picture

+ pathologic-multilingual tag.

dercheffe’s picture

Issue summary: View changes

Hi @all,

the described Issue still appears in pathologic 7.3.1

best regards
phil

lawxen’s picture

Confirm that this problem still exist on version 7.3.1

nedjo’s picture

On sites running Pathologic 7.x-3.1, some occurrences of this issue will be resolved by the fix that was committed in #2628348: Language prefix is not split off because of caching.

Anybody’s picture

Thanks @nedjo, strange - this issue just appeared magically on a project with 7.x-3.1. Absolutely no idea why it started to happen now...

Disabling pathologic fixes the issue.

dww’s picture

Version: 7.x-2.6 » 7.x-3.1

Hrm, sounds like maybe we need a 7.x-3.2 release for stuff already fixed in 7.x-3.x-dev?

I recently declared the 7.x-2.* series no longer supported. I'm not really interested in maintaining the 7.x-3.* series, but if anyone wants to test it I'd be willing to at least tag a final 7.x-3.2 release.

Anybody’s picture

Thanks @dww!
Did anyone else experience the issue in the last days or has an idea why that happened now?

Anybody’s picture

Update: Switching to 7.x-3.x-dev fixes the issue for me! I'd vote for a 7.x-3.2 release, if there are not too many risks.

mark_fullmer’s picture

I'd vote for a 7.x-3.2 release, if there are not too many risks.

Here's a list of the changes that have been committed to the 7.x-3.x branch since the release of 7.x-3.1 in 2015. Three bugs

Bug

Given this, I think it would be more beneficial to the community to cut a new release for 7.x-3.x than it would be to wait for additional work to build up.

mark_fullmer’s picture

Did anyone else experience the issue in the last days or has an idea why that happened now?

Given that #2628348: Language prefix is not split off because of caching describes a similar problem to this issue and was one of the few code changes since 7.x-3.1, could the reason that is happened "now" for you be due to a change in your site(s)' caching strategy?

Anybody’s picture

I just had a look at the drush backups and in my case pathologic 7.x-2.12 was installed before running into this issue. At 20230316194929 it was automatically replaced by drush updb with 7.x-3.1!

That caused the regression! So it seems #16:

I recently declared the 7.x-2.* series no longer supported

caused the issue for us.

As switching to 7.x-3.x-dev fixes the issues again for me, I'd vote for a new 7.x-3.2 release to fix the regression.

morenstrat’s picture

+1 for a new release. We also ran into this issue after updating from 7.x-2.12 to 7.x-3.1.

Anybody’s picture

Priority: Normal » Major

@dww could you tag a new 7.x-3.2 from current dev perhaps as of the last comments, please?

dww’s picture

Status: Active » Fixed

https://www.drupal.org/project/pathologic/releases/7.x-3.2 is now out. I managed to get my local D7 test site to where I could run this module's test suite. That's as much testing as I could spare. 😅 But @Anybody seems to have tested, so I considered it better to tag something new than to wait for weeks/months to have time for more thorough testing myself.

Thanks,
-Derek

Status: Fixed » Closed (fixed)

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