Restoring a DotNetNuke site
The MachineKey of a DotNetNuke website has been lost, which is very bad news for the user login capabilities. Luckily, this was a development site with only two users, so the downfall is minimal, but I need to get the site back up and running.
I think the only real option since there are no viable backups is to reinstall the site. However, I'm a bit worried about having to redo a lot of work. There were some menu items and content items created, which still work fine; as far as a skin goes, I believe it's using one of the default skins.
What would be the suggested course of action to restore the menu and content items after the reinstall? I'd like to minimize the amount of time required to restore the site and I'm hoping some clever database work can get me back up and running very quickly after the site is re-installed. I will do the users manually as that is negligible.
I have very little experience with DotNetNuke's database structure, but I'm very good at working with SQL databases, so if I could get some DotNetNuke-specific assistance, I should be able to work this out nicely. Thanks in advance for your help.
I think the only real option since there are no viable backups is to reinstall the site. However, I'm a bit worried about having to redo a lot of work. There were some menu items and content items created, which still work fine; as far as a skin goes, I believe it's using one of the default skins.
What would be the suggested course of action to restore the menu and content items after the reinstall? I'd like to minimize the amount of time required to restore the site and I'm hoping some clever database work can get me back up and running very quickly after the site is re-installed. I will do the users manually as that is negligible.
I have very little experience with DotNetNuke's database structure, but I'm very good at working with SQL databases, so if I could get some DotNetNuke-specific assistance, I should be able to work this out nicely. Thanks in advance for your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Option 1
You could simply choose to store password without encryption (in clear), serch "passwordFormat" in web.config
change the host password in aspnet_membership table, login in your portal
Option 2
Do anothe installation, set host password, copy in your old portal machinkey and systemkey and password and passwordsalt from new aspnet_membership to the old one, login in your old portal.
Paolo.
You could simply choose to store password without encryption (in clear), serch "passwordFormat" in web.config
change the host password in aspnet_membership table, login in your portal
Option 2
Do anothe installation, set host password, copy in your old portal machinkey and systemkey and password and passwordsalt from new aspnet_membership to the old one, login in your old portal.
Paolo.
We usually Export Portal Templates after we working from local host and upload it to live server.
Here's what we do :
1. Login as Host, and go to Host>Portals, Click on "Export Portal Templates", Choose which portal, give a name, some description, and don't forget the Check the "Include Content". Copy this two file [template_name].template and [template_name].template.r
2. Backup all your Folder Structure under Portals/[PortalID], if you had some picture that use on the Portal.
3. Remember all Module that had been installed on Portal.
Time to Upload it
1. Install all related Module same like your past portal, don't forget the skins.
2. Upload all files you had backup before. Place it into the portal create. If is new, upload it to Portals/0
3. Don't forget to Upload the two file Templates you create before, and paste it to Portals/_default
3. All we need to do last is using the Wizard. Go to Admin>Site Wizard, and now follow it step by step.
Hope is work.
Erwin