Bug: Cannot reuse old page path (5.3.3.1)

Permalink
Hey guys,

Not sure if this has been fixed in 5.4, but I wanted to make sure to mention it.

It usually seems to happen when duplicating pages. I'm not sure of the steps. Something happens and a page ends up not being able to use its path.

When you change the page's path, it looks like the same path as before, except sometimes (or all the time?) the prefix has an extra character and a slash. So, instead of saying "mysite/" then the field for setting the path, it says "mysite/i/" or maybe it says "mysite/i" then the field. I don't quite remember.

Anyhow, when you visit the path there's no page there. You have to know that the page is now actually at whatetever-you-called-it1. So if it should be "path" it is "path1" or else the page doesn't show up. You can, however, add the actual path you want to the alternate addresses, and it will redirect the real address to the internal address ... which has the 1 at the end.

Definitely a bummer for my client but not a huge deal. I've seen this happen a couple times ... always with duplicating pages (which seems a little buggy in some browsers).

Hoping this is fixed already or soon but at least it all works. The right name would be cool but this isn't a showstopper

elyon
 
Mnkras replied on at Permalink Reply
Mnkras
i have seen that as well i havn't had it happen to me on the beta yet, well see