I'm running 5.5.1 and have a weird problem with the Admin Pages control: it doesn't work. When trying to move a page under a parent page, the new page forces any existing children pages deeper in the tree (more ...'s). The menu still looks right, but the Admin Pages Control doesn't. Furthermore, the arrows to the right of the control don't work: if you try to move a child page up or down within its parent, it doesn't move. There is one exception: the Left arrow will work, but the results are not what you expect (see "clues" below).

Some clues: There are sometimes regular pages between the Admin and Host tabs on the menu. Seems I read that these have to be the last pages. If you out-dent a page, it ends up at the bottom of the list of pages, underneath the Admin page (and thus ends up between Admin and Host). It's almost like it thinks the Admin page is just an ordinary page.

I suspect a corrupt database in the table where the page order is kept. I've looked in that table and nothing looks out of the ordinary. I've had some success with out-denting pages, deleting them, then restoring them: this puts the restored page at the top of the list of pages. I then move them under a parent page. Sometimes that works (the children all end up with just "..." before them) and sometimes is doesn't (the new child pushes the existing children deeper (they get "......" before them as if they are now children of the new child page). However, even after that, the actual menu still looks like a parent with only children (no children/children).

Help. Please. Anyone seen this before?

Troy

Yes, I had the same issues with Pages in DNN 5.x. I gave up on it and used the Ribon Bar > Current Page to move pages around.

Thanks for the info. I tried that, but the behavior didn't change. I did upgrade to 5.6 and that didn't help. I'm now in the process of upgrading to 6.X. I don't think that will help if the db is corrupt, but the control for moving pages is completely different - drag and drop - so I'm hoping that will help. I'll update this post after that's done.

If the problem is in the database, upgrading won't solve the problem. It may, though, give you a better tool to use.

I would suggest that you do your work or experimentation on a copy of your site. Once you get things fixed, you can move it to your live site.

One thing that you might consider doing is moving all of the pages to the top level, or do that for some of the pages with problems. Then you can redo the parent/child relationships. Certainly the new drag&drop interface in 6.0 will help. If you don't want to upgrade to 6, you can get the same functionality as the module is available for DotNetNuke 5.x at codeplex.com. Look for modules from DNNWerk to locate it easily. You can install this module on the same Admin, Pages page and have both versions at the same time - if you want to do things that way.

Here's the latest: The upgrade to 6.0 worked but so didn't the addition of the DNNWerk module on the 5.6 site. My suspicion is that the 6.0 control IS the DNNWerk module (the icons were the same), but I could be wrong. So, it appears that the database wasn't the culprit, but the control itself. Still some questions out there: we updated from 5.5 to 5.6 and that didn't help but maybe it didn't update that particular control. Who knows? We did have several local versions running in the office so as to not further damage the production site. We're in the process of implementing the change on a local copy of the production siite and if that works, we'll upload that to the host site.

In any case, thank you all for the tips and advice. Again.

Yes, the DNNWerk module is the new Pages module for DotNetNuke 6.0. The User Accounts module is also a DNNWerk module, or an adaptation of it. Both of those modules are available for earlier versions, but I'm not sure how far back they will work.

Latest update: we started having problems again with pages even with the new control. Pages would randomly disappear shortly after being created. In looking at the database, sometimes the record would be there but a -1 in a key field and a "deleted" text in some other field. In other cases, the pages did in fact completely disappear with no trace in the database. So, we've moved to Plan B: a whole new installation. We downloaded 5.6 and did clean install with a new database. I did put the DNNWerk module back on - just like that control better. Our first step was to load the skin (Flex2) and then to add empty pages back (about 65 of them) manually. Everything worked for a while, then pages started moving around randomly. Every now and then, 2 or 3 of the root-level pages will end up between Admin and Host. And sometimes the root pages change places. It's like DNN cant keep track of the tab IDs and the order they're supposed to be in. I'm going to start a new thread to see if anyone else has seen this.