whoops, hadn't had a chance to update this thread.

Last night a decision was made that a 4.8.5 release will happen to resolve a few high/critical fixes - the fix for friendlyurl's is one of these. I checked it in last night, and have another fix I plan on resolving tonight. I'm not sure what the timeline is , but the scope is not very large, I think it's only another 1 or 2 issues so it won't be too long until 4.8.5 is out (as usual you can check via the roadmap @ http://support.dotnetnuke.com/project/RoadMap.aspx?PROJID=2)

Cathal

Brian, I validated and updated the issue with the relevant details (http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=7927&PROJID=2). I believe this has always been a problem (i see no evidence that this renaming child portals ever worked - renaming parent portals would have always worked). As the scope for 4.8.5 is tight, I would not expect it to make it. I added notes in the issue to show the 2 different ways to resolve this, either you can use the host portal url to revert to the original url, or if you need a new child portal url, you can simply rename the folder. Hopefully that is sufficent to fix your issues until this can be worked on for a future release.

Cathal

Thanks for the update Cathal, any rough idea on when 4.8.5 will be released???