Hi,

We recently updated pathauto expecting our current configuration to remain the same - instead it now adds the string 'amp' where-ever it finds an ampersand in the [menupath] despite the checkbox to remove them being ticked (as it always has been).

Am I wrong, or should a module update not break a site apart if you don't change any options? This seems to me to be a bug.

I've been reading something about -raw attributes on the pathauto configuration page but surely I shouldn't need to change my configuration to keep the paths I had in a previous version? In fact I'm quite keen not to do this since I suspect getting it wrong could have dire consequences.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Update to latest pathauto breaks site's paths » pattern changes are confusing/unexpected to upgraders
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Well, a change from 5.x-1.0 to 5.x-1.1 should stay consistent and in fact it did.

A change from 5.x-1.0 to 5.x-2.0 is a change in version number and in the release note I encouraged people to read the upgrade notes.

That page describes why the patterns had to change. I'm sorry that they did, but they did have to change. If you have some ideas on how to make this transition easier for people to deal with then please let me know.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Ok, I guess there's nothing to do.