Hi Al, as far as I know, in the "big picture" a page is a page, so there is really no distinction between parent and child pages, the hierarchy just comes from where they are located in the menu, combined with the menu structure and CSS, and they can be rearranged at any time (one of the most powerful features of using a CMS).

When you create a new page, the default contents of the "URL" field comes from what you put into the Page Name field, but you can override that. So if the new page you created is called "KBA1010 - My First Product", once you tab out of the Page Name field, the default URL will be set to "~/kba1010-my-first-product.aspx". Then you can just manually override that URL field to be "~/kba1010.aspx", as long as that's a unique URL in the system, and your page will be located at ~/kba1010.aspx. As long as you make this change during the initial page creation, you won't have to worry about updating any redirects through the 301 Redirect Manager.

Hopefully I understood what you are trying to do.

Jamie

Okay, now I see what you mean. I agree that it would be an improvement if Page Settings would distinguish between a brand new page and a page update, and not automatically change the URL if the page name is changed during settings update of an existing page. I think that would be a good enhancement, assuming Joe agrees.

I know what you mean about the collaborative editing issues. Soon we're also going to have to face all the training issues that will come with that, but overall I know the upsides will really make it all worthwhile!

Jamie

Hi guys, I think I agree with Joe D. that it should probably be a confirmation at save time rather than an invisible config setting (or a confirmation that's enabled via config setting). That way the user will be given a message and possibly an extended help button so they can understand the ramifications of changing the URL after it's been established. I'd think that pages are renamed infrequently enough that an extra confirmation wouldn't be a burden to users, and it seems like we've had a few messages on the forum lately dealing with folks not knowing about/understanding the 301 Redirect Manager.

Jamie