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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.0.2 and virtual directoriesDNN 6.0.2 and virtual directories
Previous
 
Next
New Post
10/16/2011 7:36 AM
 
I am trying to migrate a legacy HTML web site to DNN and have the top structure migrated but a lot of the old articles are still in the old site.  My test site is in one domain and my legacy site is in another.  I want to point the legacy domain at the new DNN site.  In order to avoid creating broken links for those who may have linked deep into the legacy site, I created virtual directories for the key content from the old site under the DNN IIS 7.0 site.  I did most of the build under DNN 5.6.2.

Over the weekend I upgraded from 5.6.2 to 5.6.3 and then to 6.0.2.  My base portal worked as expected with the nice popup menus.  My site did not.  The base portal was setup on one IIS site, and the real site portal was set up as a separate site.  I could not see a difference in the way that they were set up.  Eventually I created a fresh test portal under the site portal IIS site.  This didn't work either.  After much head scratching I unbound the test site from the site portal IIS and bound it to the base portal IIS.  Everything worked!  So it seemed there was some minor difference between the two setups.  I assumed something to do with the App Pool.  So I bound all the target domains under the one IIS site.  All was happy.  Then I recreated the virtual directories under the other site.  12 hours later, the sites are back to the not working state.  It's fine when not logged in, but as soon as you log in as host, the header for view/edit/layout is not rendered correctly and the popup menus fail.  It looks like some CSS is not being loaded.

Is there something about using virtual directories with a DNN site that is screwing this up I'm missing, or could there be something else subtle going on once I add the virtual directories.

Thanks for any suggestions you may be able to provide.

Warm regards,
Bob Reimer
Al Ain
United Arab Emirates



 
New Post
10/20/2011 2:56 PM
 
Just in case someone makes the same mistake I did, the resolution is that one of the virtual directories I added was called "resources".  This of course masked the Resources directory that is part of DNN, therefore all the scripts and style sheets in that directory couldn't be found causing the problem I saw of being unable to edit the site.  The moral of the story is to be careful when adding virtual directories under the DNN root directory that you aren't masking a directory that's in use.  I added the directories inside the directory I wanted from "resources" as virtual directories inside of the actual DNN "Resources" directory.and everything worked the way I needed it to.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.0.2 and virtual directoriesDNN 6.0.2 and virtual directories


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