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
Comment #1
canrull CreditAttribution: canrull commentedI 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.
Comment #2
Garrett Albright CreditAttribution: Garrett Albright commentedOkay, thanks for your feedback. With a lack of any new reports of problems on this, I'm going to go ahead and close this.
Comment #4
funkytraffic CreditAttribution: funkytraffic commentedI 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.
Comment #5
Garrett Albright CreditAttribution: Garrett Albright commentedDid you mean "Pathologic" instead of "Pathauto?"
Is this happening on all paths, or just paths to files?
Comment #6
funkytraffic CreditAttribution: funkytraffic commentedOf course I meant "pathologic", excuse me.
Comment #7
Garrett Albright CreditAttribution: Garrett Albright commentedIs 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.
Comment #8
funkytraffic CreditAttribution: funkytraffic commentedThis bug appeared on all paths.
The dev seems to correct the bug in my case.
Comment #9
hass CreditAttribution: hass commentedDEV does not output the aliases. #1885490: Paths not converted to aliases
Comment #10
Garrett Albright CreditAttribution: Garrett Albright commented+ pathologic-multilingual tag.
Comment #12
dercheffeHi @all,
the described Issue still appears in pathologic 7.3.1
best regards
phil
Comment #13
lawxen CreditAttribution: lawxen at Sparkpad commentedConfirm that this problem still exist on version 7.3.1
Comment #14
nedjoOn 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.
Comment #15
AnybodyThanks @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.
Comment #16
dwwHrm, 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.
Comment #17
AnybodyThanks @dww!
Did anyone else experience the issue in the last days or has an idea why that happened now?
Comment #18
AnybodyUpdate: 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.
Comment #19
mark_fullmerHere'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.
Comment #20
mark_fullmerGiven 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?
Comment #21
AnybodyI 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:
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.
Comment #22
morenstrat+1 for a new release. We also ran into this issue after updating from 7.x-2.12 to 7.x-3.1.
Comment #23
Anybody@dww could you tag a new 7.x-3.2 from current dev perhaps as of the last comments, please?
Comment #24
dwwhttps://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