I've opened to fix the warning.

My instinct is to keep the old aliases as if someone bookmarked the old URL we can keep the old alias working for them.

Thanks, closed the issue.

This issue doesn't work well in trunk now as there isn't any caching of getAliases() as got reverse merged.

I'm curious why this ticket is still open with commits from 2008 and affects version qa06.

I'm seeing an issue with this if you have this feature enabled. If you change the language in your site, it generates entirely new aliases and prints up a warning message every page refresh.

2014-05-13 14:33:22,873 WARN http-bio-8080-exec-16 org.sakaiproject.portal.api.PortalSiteHelper - More than one alias for: 9814ac27-3b7e-44a9-8c53-dc30aa8ee0d5:05014940-3d34-44bb-bc08-db8c1a013ce2

/pagealias/9814ac27-3b7e-44a9-8c53-dc30aa8ee0d5/forums <-> /pagealias/9814ac27-3b7e-44a9-8c53-dc30aa8ee0d5/foros. I'm not sure about a super fix for this? Clean up the old ids if the language is changed? I guess this is a new issue.

Well caught. It was just an arbitrary limit, I've upped the default to 15 and it's also configurable through sakai.properties:

maxLength@org.sakaiproject.portal.service.AliasingSiteAdvisor=22

Why limit aliases to 12 characters specifically? Sadly this causes Announcements to get truncated in the URL. Perhaps a more generous limit like 15?