Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving from Development to Live Environment - Help Needed. Moving from Development to Live Environment - Help Needed.
Previous
 
Next
New Post
9/18/2007 12:49 PM
 

Howdy,

I am working on dotnetnuke setup and I am having some issues. 

I have a development site and I want to separate that out with a live site. First does anyone have any whitepapers, links, or info on the best way to go about doing this.

Current setup is using SQLExpress database, that I have been attempting to copy one (the dev) database to another (the live) database using the Import Export Wizard in SQL Management Tools. I then simply change the web.config to point to the new live database. 

I have noticed it does not appear to copy everything from Dev, to Live. It leaves out some of the Security - Database Application - Roles, as well as some of the database views. Not sure if this is an issue or not, but the error message I am receiving:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'requirePermission'.

Source Error:

Line 4:      <sectionGroup name="dotnetnuke">
Line 5:        <!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support-->
Line 6:        <section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
Line 7:        <section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
Line 8:        <section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

Any help would be appreciated thanks!
Dd.

 
New Post
9/18/2007 1:56 PM
 

Hi Ddraig,

I have successfully done what you are trying to do. I'll try to describe what I do when I update the DB because you'll need to have full control on your host/ live site. I also have locally SQL Server 2005 Express with Advanced Services installed, and my host has SQL Server 2005.

1. first of all, you will need to add the correct alias to the PortalAlias table in the DNN DB; it should at least have two for each PortalID: one for your local path (without using http:// nor pointing to the page, just the directory where default.aspx lives is enough) and the other for when the DB is live. Make sure the live alias is the correct one!

2. before I make a backup of the DB locally, I run some scripts to change the image paths for the modules that use HTML content, images, and also javascript that gets injected is checked

3. then I make the backup, zip it and upload it onto a folder on my website

4. then in my panel I browse to my SQL Server 2005 DB, and select RESTORE (my host on www.dotnetpark.com does luckily provide this very useful option)

5. I point to the zipped DB, and press Restore button, and voilá

6. all DNN logins work, the alias is correct, and also the image paths are correct, the only ones that I haven't tackled yet are the ones inside the templates

I hope this makes sense, if anyone is interested I can post an example of the script I'm using to change image paths.

PD: this procedure may fail if the host has poor DB support, currently I am facing a similar case, so please take care in choosing your DNN host!

PD2: I do all this stuff because I need the dev process afap (f=fast) and it works really great for me!  

Cheers, Pieter

 
New Post
9/18/2007 2:02 PM
 

Sorry, I forgot to add that you'll need to modify the connection string(s) in web.config if necessary, before pointing to the Default.aspx file.

PD: You may see sometimes that DNN first updates the site, this happens when DNN / DB versions are different, but until now I didn't have any problem with that, as long as you work in 4.x you should be fine.

Cheers, Pieter

 
New Post
9/18/2007 2:32 PM
 

Hi Pieter,

Thanks for the quick response. This does help me, but not exactly sure it answers/resolves my issue. I would love to see the scripts you are using as I will most likely need to use them.

The first step I was able to accomplish.

I have full access to the server that these databases are one, they're on the same instance of SQL 2005 Express, and I am creating a duplicate of a database on the same sql server.

It isn't an ideal situation but my development site is on my live server so I am really not doing any uploading of files its more of a case of copying folders over and making sure I have permissions correct and things. I'll have to try your steps for exporting the sql 2005 express database though.

Thanks again,
Dd.

 
New Post
9/19/2007 10:35 AM
 

Anyone have any else have any insight into this problem? Could really use some help or a good article to read.

Thanks,
Dd.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving from Development to Live Environment - Help Needed. Moving from Development to Live Environment - Help Needed.


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out