penghh wrote
I have a DNN installation with many portals. But I want to move one portal to other DNN Installation. For example. I want to move my portal from A hosting provider to B hosting provider. I have only the administrator permission, not the host permission.
How can I do this? How to backup my portal and move to another host to restore it?
Could anybody help me?
You can backup the entire database via sql (at host a), and copy the dotnetnuke root directory. Create a new database (at host b) restore the database, and copy the root directory over to host b. Then set up IIS at host b and point it at your dotnetnuke root. Once you update the DNS records host b should be up and running. There are some threads in the forum on how to set a lost host password. You'll need to go into the aspnet_membership table and copy the password and password salt from a know user/password to the host user. You might need to check the aspnet_users table to make sure of which user is "host". You could also go into the users table and put a 1 for "IsSuperUser" under your username. That should grant your username host access.
But as I read further in the thread I see that the issue is more complex, more like what I'm working on right now.
Extracting ONE portal out of one dotnetnuke codebase...and then
Putting that ONE portal into an existing code base that already contains multiple portals..
Anyone seen a forum thread, webpage, or module that addresses how/what the issues are and what needs to be done to make this a reality?
I can see all kinds of issues:
- users
- tabids
- module ids
- module defs
- file structure changes from the portal number changing
I tried to export a template including content. Thats FAR from a perfect solution...
Anyone?
Bent Angle