Duplicate language prefixes in path on multilingual sites

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 → .

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...

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.

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

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.

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

• #2789953 → by Dave Reid → , junaidpv → , Anybody → , mark_fullmer → , hiraethmarkb → : Do not set NULL for $options['query']
• #1958122 → by fietserwin → , herved → : Pathologic should handle not yet created image derivatives as if they are files
• #2628348 → by jurgenhaas → : Language prefix is not split off because of caching

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.

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?

I just had a look at the drush backups and in my case pathologic 7.x-2.12 was installed. At 20230316194929 it was 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.

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

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

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

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