Since 5.4.1 I've been noticing some buggy behavior in the page/tab management. Particularly, when I've been setting up sub-pages, when I go back to adding root-level pages, if I choose / leave selected the Parent Page option as "none defined" - the "Before/After/At End" option still uses the previous submenu options I was working on, and not the root-level items.  If I leave it untouched, it puts the new page at the beginning of the root list.

Also, if I accidentally place and item in the root and later edit it to have a parent page, when I go to Admin > Pages, the treeview shows the page at the root level, and I'm unable to move it's placement within the subpages (move it up/down the list).

I didn't see this fix in 5.4.2 so I wasn't sure if this had been addressed, but I've seen the same behavior across ~3 new sites using 5.4.1. Has anyone else encountered this?

Thanks!

My experience with 5.4.1:

I added a page and forgot to enter the parental page. After trying to move the page to the correct level using the arrows on the right side of the page list the new page was lost.

When I try to enter a new page with this name I get an error:

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Tab Exists ---> DotNetNuke.Entities.Tabs.TabExistsException: Tab Exists at DotNetNuke.Entities.Tabs.TabController.AddTabInternal(TabInfo objTab, Boolean includeAllTabsModules) at DotNetNuke.Entities.Tabs.TabController.AddTabBefore(TabInfo objTab, Int32 beforeTabId) at DotNetNuke.Modules.Admin.Tabs.ManageTabs.SaveTabData(String strAction) at DotNetNuke.Modules.Admin.Tabs.ManageTabs.cmdUpdate_Click(Object Sender, EventArgs e) --- End of inner exception stack trace ---

Is it possible to reactivate the page directly (iE in the MS SQL tables)?