![]() |
| dotnetnuke |
|
tbhaddix
|
I was thinking about installing dotnetnuke. Is there anything I should know beforehand?
|
||||||||||||
|
|
|||||||||||||
|
bobum
Elvis Fanatic
![]()
|
It can be a pain in the A$$ but I have a 2.1.2 installation up and running on HMS at www.davisplanet.com if you wanna take a gander at it - forgive the skin - it sucks and is only temporary.
Mine right now is using the default MSAccess database since HMS doesn't offer a SQLServer db with their lower end installations. But it's ok for now. I'm running a few plugins which I have for DL on that site as well. I really like DNN and have 3 other sites using it on another host. One DNN installation is running all three of those sites. |
||||||||||||
|
|
|||||||||||||
|
tbhaddix
|
thanks. i'm going to give it a try in the next few days sometime. the readme file says something about setting up a virtual directory, do i need to do this, or will it work if i just install into my root directory?
|
||||||||||||
|
|
|||||||||||||
|
bobum
Elvis Fanatic
![]()
|
You will probably need to get HMS to set up your DNN installation as an application. This will create the virtual directory on the IIS server automatically. I am also pretty sure they will have to grant NETWORK SERVICE modify permission to the root of your installation and cascade it to all child objects.
The best thing to do is to install DNN in the root of your HMS directory - the way DNN parses URL's will work best and with least modification if you install it in your root. Otherwise you're going to run into all kinds of wierd problems. So install to root, get HMS to make it an application in IIS, then ask for NETWORK SERVICE to be granted modify permission to root and cascade to children and you should be well on your way. Your next hurdle will probably be setting up the portal alias's...That always seems to be peoples next problem...I'll wait and see...hehe |
||||||||||||
|
|
|||||||||||||
| dotnetnuke |
|
||
|



