Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogRead More link give me XML Parsing Error: no element foundRead More link give me XML Parsing Error: no element found
Previous
 
Next
New Post
12/30/2008 2:33 AM
 

Hi Karl,

running DNN locally, if you wish to change the website folder for your local install, you first need to change the folder's name under the file system. You can use the default Windows explorer. Then you will face one of the two scenarios:

  1. You are using IIS to run locally, you may probably see http://localhst/DNNWebsite in your browser address bar. To update IIS settings, locate the website under IIS, right click on it and update the website folder. You will need to locate the new folder name for the physical website location, and insert the virtual folder name you desire.
  2. You are running VS or VS express, and using the internal server, so the address you see is like http://localhst:1315/DNNWebsite, in this case you don't need to do anything, because the IDE will automatically create the website virtual folder and run it for you matching your changes to the phisycal folder name.

In both case, at the end, you'll need to open the PortalAlias table in your DNN database, and update the HTTPAlias field to match your changes.

Best regards,
Dario Rossa

 
New Post
12/30/2008 4:56 AM
 

Thanks Dario,

I am running VS2008. To keep track of the versions, I have named this one DNN500b. In my HTTPAlias field I have localhost/dnn500b which is reflected in my PortalAlias table.  I can't see any 'spaces' in any names. The original compile works. As soon as I try a second compile I get the errormessages regarding the FCK Editor.

Regards

Karl

 
New Post
12/30/2008 6:06 AM
 

Hi Karl,

same issue here, I'm using the 05.00.00 install version by the way. Right click on the website in the Solution Explorer and chose Add Reference. Select bin/Providers/DotNetNuke.FckHtmlEditorProvider.dll. The solution should magically build.

Best regards,
Dario Rossa

 
New Post
12/30/2008 9:24 AM
 

Thanks, Dario - that did the trick, Happy New Year, Karl

 
New Post
12/30/2008 10:08 AM
 

Thanks, Dario - that did the trick, Happy New Year, Karl

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogRead More link give me XML Parsing Error: no element foundRead More link give me XML Parsing Error: no element found


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