I've lost the portal with portalID 0 in a couple of DNN installs as a result of splitting out DNN installs to get single-portal DNN installs for certain portals.

Now I have a need to implement a module that depends on the existence of portal with portalid 0.

I am looking at creating a new portal which will have a different PortalID initially, and then updating all instances of PortalID to be 0 for that portal.

Anyone done this before, and know just how many tables I'll have to touch?

portals
portalalias
profile
profilepropertydefinition
rolegroups
roles
sitelog
skins
systemmessages
tabs
urls
urltracking
userportals
usersonline
vendors

<others?>

if exist in any of those (may not in all)
I won't deploy any modules or do any editing of content before trying to move portalID n to PortalID 0.

I will, of course, take a copy of the DNN install and set it up locally and practice there first, and test.

Any thoughts / experiences / advice welcome.

---

pmgerholdt

I recently had to split off a single portal from a multi-portal install and although I initially thought it would be good to adjust all references to this site's PortalID (6) to 0 in the database I soon decided that it would not only be a time-consuming but also difficult process due to the many foreign key relationships on PortalID between various core and third party tables.

As Sebastian indicated, a module should not depend on the existance of a portal with PortalID = 0. I would suggest that you contact the module developer or if you are the developer, reconsider this dependency.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner