Hi All, I created a portal under a shared instance of DNN do the URL would be something like this. http://www.localinstance.com/portalname I already have a website on http://www.portalname.com. Now I want to make the DNN site the active site. I know I can go into IIS and change the directory and point it to the DNN portal directory, however, my question is can I copy the portalname directory to the .com site? Or, when I create a "child" can I put it into that site or does it have to be under the "instance" domain? Hope you can follow my logic here.


Peter

hi Peter,

I'm a bit confused with what you're saying here, however, if you are asking can a child portal be converted to a parent portal with a new domain name, then the answer is yes.

All you have to do is change the portal alias URL for that child portal and it will become a parent portal (just make sure you get the correct formatting for a full URL). - you will need to make the necessary changes in IIS and point the additional domain name to your DotNetNuke installation files.

Thanks,

no, what I am asking is.... I have an existing Domain call it Bagels.com it's a standard html web site. I put up a "bagels" child on one of my DNN instances so I have a URL that reads http://www.wildpony.com/bagels. I know I can point through IIS. My question is, either for now or future sites, how can I transfer the files from the directory under wildpony to the bagels.com so it's not under the Wildpony directory? (i know it's confusing)

Peter

I'm getting confused, too! 

Do you want to move your child "bagels" site to Bagels.com?  The easiest thing to do is to alter DNS to point Bagels.com at your DotNetNuke installation.  Then, add a Bagels.com portalalias to your child site.

Yeah I know what you mean. Let's try to rephrase this. I have the bagels.com domain with a standard front page created site.
I started to work on a new site for them at wildpony.com/bagels

I know I can alter the DNS and just point bagels.com to the "child" on wildpony.com/bagels

My question is can I move the "child" into the existing bagels.com domain directory and point the DotNetNuke instance to that directory?

Peter

If I'm understanding, the answer is no.

There are no "pages" to move. DotNetNuke is a web application and the "pages" are created dynamically. There is nothing to move.

OK Thanks. That's what I thought. I was just getting (bad) "tech" advice from a server guy that said the portal should be directly under the domain. I tried to explain that If I set up an instance at the "bagels" domain, than the directory would be there. But because it's under a "child" / "parent" portal, it remains under that instance.


Peter

My guess is that the server guy doesn't know about DotNetNuke ...

<!--[if gte mso 9]> ocumentProperties> 宗聖1 12.00 ocumentProperties> <!--[if gte mso 9]> Normal 0 unctuationKerning/> isplayHorizontalDrawingGridEvery>0isplayHorizontalDrawingGridEvery> isplayVerticalDrawingGridEvery>2isplayVerticalDrawingGridEvery> false false false oNotPromoteQF/> EN-US ZH-TW X-NONE oNotLeaveBackslashAlone/> oNotExpandShiftReturn/> ontGrowAutofit/> ontVertAlignCellWithSp/> ontBreakConstrainedForcedTables/> ontVertAlignInTxbx/> MicrosoftInternetExplorer4 <!-- /* Font Definitions */ @font-face {font-family:新細明體; panose-1:2 2 5 0 0 0 0 0 0 0; mso-font-altMingLiU; mso-font-charset:136; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611969 684719354 22 0 1048577 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Cambria; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1073741899 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"\@新細明體"; panose-1:2 2 5 0 0 0 0 0 0 0; mso-font-charset:136; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611969 684719354 22 0 1048577 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:none; font-size:12.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:新細明體; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-font-kerning:1.0pt;} h1 {mso-style-priority:9; mso-style-unhide:no; mso-style-qformat:yes; mso-style-link:"Heading 1 Char"; mso-style-next:Normal; margin-top:9.0pt; margin-right:0cm; margin-bottom:9.0pt; margin-left:0cm; line-height:300%; mso-pagination:none; page-break-after:avoid; mso-outline-level:1; font-size:26.0pt; font-family:"Cambria","serif"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:major-latin; mso-fareast-font-family:新細明體; mso-fareast-theme-font:major-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:major-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:major-bidi; mso-font-kerning:26.0pt;} span.Heading1Char {mso-style-name:"Heading 1 Char"; mso-style-priority:9; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Heading 1"; mso-ansi-font-size:26.0pt; mso-bidi-font-size:26.0pt; font-family:"Cambria","serif"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:major-latin; mso-fareast-font-family:新細明體; mso-fareast-theme-font:major-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:major-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:major-bidi; mso-font-kerning:26.0pt; font-weight:bold;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} /* Page Definitions */ @page {mso-page-border-surround-header:no; mso-page-border-surround-footer:no;} @page Section1 {size:595.3pt 841.9pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:42.55pt; mso-footer-margin:49.6pt; mso-paper-source:0; layout-grid:18.0pt;} div.Section1 {page:Section1;} --> <!--[if gte mso 10]> Hi Joe,

 

I have similar but slightly different situation in my case here:

 

I have two old purely html hosting sites and I have created a sub-domain in each of the site, then installed DotNetNuke (5.0.1 and 4.9.3) and working properly in these sub-domains with some different testing demo sites as child portals as well, also I have utilized some 3^rd parties’ modules like IndooGrid and DNN360-7modules (CISS.FlashPlayers, NavigationSuite, SPSKIN3_01, FlashChart, tab2.3.8 etc..) in it.

 

After the test mode was performed very fine, then we are try to move the portal to the root of the main domain web folder from the sub-domain; I have add a new alias as RootDomainName.com and copied the whole web folder (DNN installed) to the root web folders, including the web.config (pointed to the same SQL 2005 database), and asked my hosting provider to setup the permission for the root web folder for me.

 

But after I entered "http://www.RootDomainName.com/default.aspx" instead of the old working one "http://Subdomain.RootDomainName.com/default.aspx" it comes out an error message

 

Server Error in '/' Application.

Cannot register or retrieve components until ComponentFactory.Container is set

 

Please tell me what I have done wrong here? and how to resolve this issue?

I have tried the …..com/install/install.aspx but not help either.

 

Thank you,

 

Jesse L

Did you change the portalalias table?

Yes, I have add a new alias as RootDomainName.com in the PortalAlias table and a localhost/NewVirtualName in it as well

Thank you,

Jesse L

Hello Joe,

I am sending with attachments to describe my issue here, hope you can diagnostic my problem and help me out here,

Many thanks,

Jesse L

There aren't any attachments.

<!--[if gte mso 9]> Normal 0 unctuationKerning/> isplayHorizontalDrawingGridEvery>0isplayHorizontalDrawingGridEvery> isplayVerticalDrawingGridEvery>2isplayVerticalDrawingGridEvery> false false false oNotPromoteQF/> EN-US ZH-TW X-NONE oNotLeaveBackslashAlone/> oNotExpandShiftReturn/> ontGrowAutofit/> ontVertAlignCellWithSp/> ontBreakConstrainedForcedTables/> ontVertAlignInTxbx/> MicrosoftInternetExplorer4 <!-- /* Font Definitions */ @font-face {font-family:新細明體; panose-1:2 2 5 0 0 0 0 0 0 0; mso-font-altMingLiU; mso-font-charset:136; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611969 684719354 22 0 1048577 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"\@新細明體"; panose-1:2 2 5 0 0 0 0 0 0 0; mso-font-charset:136; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611969 684719354 22 0 1048577 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:none; font-size:12.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:新細明體; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-font-kerning:1.0pt;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} /* Page Definitions */ @page {mso-page-border-surround-header:no; mso-page-border-surround-footer:no;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> <!--[if gte mso 10]> It is very odd, it wound not take MS word format file, let me just redo it in a txt format again.

 

Sorry for the confusing and thank you for help,

 

Jesse L

Hey Digisoft, when you said you "moved" the subfolder, did you actually move it? You should just have to go into IIS and point it to the subfolder as your main folder. No need to physically move the folder.

Hello Peter,

Thank you for your information.

Yes, I agree with you, it is a very good point, but set the URL to the sub-domain (subfolder) or have the provider to set DNS is my last option. Because I just need to figure out what I have done wrong here before I can take further action on the other DNN 5.0.1 installation in the same scenario.

What I mean on “move” is I have just copied the entire web folder of the working sub-domain site (DNN 4.9.3) to my root domain web folder; but keeps the sub-domain still running in the “http://SubDomain.DomainName.com/defaut.aspx.”

So far my root domain is only dealing with the old pure html file as the default web page, and it trigger the (damaged/un-working) DNN site in the root only if we entered “http://DomainName.com/default.aspx”.

I thought it should not have problem to “Move” a DNN site from one location to the other, if I do it right on the following tasks.
1. Backup/Restore the SQL server database with correct user rights and setting.
2. Duplicate the working copy of DotNetNuke web folder/files and configure it with correct user permission setting on the new target location web folder/files.
3. Have a correct copy of web.config file.
4. Maybe some 3rd parties’ modules need to be take care (not sure in this).

But that was not it, every time I “Move” (duplicate) the installed site such as from localhost (Vista Premium IIS 7) to live hosting, from hosting site to localhost and this time just duplicated it from the subfolder to the root of the site in the same provider, all follow the steps that I have learned form dnnCreative (the best DotNetNuke learning resource), but never have any luck in this. Every time I have end up starting it again from the scratch.

I will appreciate if anyone there can help me to resolve this issue.

Regards,

Jesse L

Jesse... Why are you trying to make it so complicated? any time you "move" the original install you are creating problems. I do agree that DNNCREATIVE is a tremendous source so stick to the principal KISS.

Peter,

For your information, I am planning to change all my customers’ web sites into DNN frameworks, but in order to convince them through the internet, Instead of install them on localhost I have re-implement their sites as DNN sites by created some demo sites in different sub-domains (mostly in different installation) of my other DotNetNuke hosting sites for currently none DotNetNuke hosting clients.

After they have satisfied the looks and features and are ready for launch the new production site, I am trying to avoid re do these same works again if I can just “Move” them as everybody does it to move from localhost to the live hosting.

Thank you,

Jesse L

I would recommend that you assign a temporary URL to the developmental sites.  Then, when they are ready to "go live" you can assign the live URL.  This will requre an adjustment to the website in IIS and an addition to the portalalias table.

Jesse,

In that case I would stick with one or two "clean" installs to do this. If you are using live DNN sites it's a little more difficult to make the move. Remember DNN is a database driven architecture. When you backup the DNN site "database" you can than restore to the clean site along with the infrastructure. But if you do it from a site that already hase other "sites" than you are bringing over things from that database.

Lee has some good tutorials you should watch on Transfering a site.
Transferring DotNetNuke Installations:
How to backup a live hosted DotNetNuke website and restore it to a localhost installation
How to transfer a localhost DotNetNuke installation to a live website
Find and Replace SQL queries for DotNetNuke (To fix problems after transferring a localhost database to a live website and other useful functions)