Installation on GoDaddy is problematic mainly due to the requirement to install DotNetNuke in a subfolder of the website.

There are three solutions:

  1. Get a proper webhost before you go any further - This is the recommended solution if you consider your time valuable.
  2. Use the GoDaddy wizard and try to revise the store module afterwards - See below
  3. Use the workaround detailed below to install DNN at root where it should be.

Use the GoDaddy wizard and try to revise the store module afterwards.

Note that this method is not supported and the information provided here may or may not be complete when it's your turn to make the attempt. Read this thread for details.

In NB Store 2.1.7, the following templates will need to have the DNN subfolder name added to the paths in these templates. This is typically done where you can see "/tabid" or "/DesktopModules".
  • stylesheet.css - search for 'url' and add the subfolder name to the paths.
  • nowishlist.template - once
  • productdetail.template - a few places at the bottom
  • soldoutimg.template - once
  • minicart.template - a few places
  • minicartempty.template - once
  • emptycart.text - once
  • stgheader1.template - once
  • stgheader2.template - once
  • stgheader3.template - once
  • stgheader5.template - once
  • ordersreport.xsl - once

Also, in the category menu module settings, find "Tree Title Html" and apply the full path to your actual store page.

Install DNN at your GoDaddy root

This procedure is supplied by ccaspers.
Note that this method is not officially supported by either GoDaddy or NB_Store. Read this thread for further details.
  1. DO NOT use Go Daddy installation application wizard to install DNN, as it forces a DNN install in a sub-folder, which causes some issues in some modules (NB Store for example)
  2. Using the wizard forces you to exclude remote access to your database; as developers, we like to use Visual Studio and Enterprise manager to remotely connect to our databases. Instead, install DNN manually. Also, install your database instance manually in order to enable remote access. The following briefly describes a CLEAN DNN installation where not every step required for keeping an old website in tact is included.
  3. Before doing anything, FIRST BACK UP your database using the Go Daddy SQL database backup utility
  4. If you have DNN installed in a folder and you used Go Daddy wizard, uninstall DNN with the wizard and have it delete your backed up database.
  5. In go Daddy Hosting Control Center/Content/IIS Management, check the subfolder that DNN sat in and click on the X mark to delete the application (no use leaving garbage on your website)
  6. By default, Go Daddy DOES NOT set Write rights on the root folder and therefore children won’t get the correct permissions; you will change this by first going to the Go Daddy HOSTING CONTROL CENTER/Content/File Manager tool, checking off Root folder and then clicking the Permissions icon
  7. Next, a panel opens that allows you to make changes to Read/Write permissions; ensure that Read and Write are checked and that Reset all children to inherit is checked (just for safety) and click the OK button to apply changes; now when you install files and folders to the root, they will inherit Read and Write rights
  8. Remote database access is required if you want to connect using Visual Studio and/or Enterprise Manager. If you desire remote access to your database than do steps 9 to 11; otherwise, skip to step 12.
  9. If you have a free slot for installing a MS SQL database, than create a new database and ENSURE that Allow Remote Access (wording not exact here) is checked (this will be where your new DNN install will point (web.config will be modified)
  10. If you do not have a free MS SQL slot (basic hosting only gives 1 MS SQL database), than delete the database (MAKE SURE YOU'VE BACKED UP FIRST) and install a new MS SQL database with remote access checked
  11. If you installed a new database, but desire to have your old website back, restore the backup file to the newly created database using Go Daddy MS SQL restore database feature; keep in mind that we only went through this process in order to have a database that has remote access enabled
  12. Get the copy of DNN install zip for Dot Net Nuke and use the Hosting Control Center/ Content/File Manager/Upload feature to upload to ROOT of your host
  13. Now use the same tool to check the ZIP file and Unarchive files to the root; DO NOT run your website yet
  14. Using same tool; download the web.config file and modify it to point to your new database # If you are using your OLD database, modify records in table PortalAlias of your Dot Net Nuke database so that the HTTPAlias no longer refers to the subfolder; for example, I had an entry that pointed to “localhost/dnn/ladybugs” and changed it to “localhost/ladybugs.”
  15. Once you have your NEW or OLD database ready and you have your fresh DNN pointing to your database of choice, browse to your DNN site and it should initiate the installation (for new DNN database) or run your website with your old database

Please ask questions in this thread.

Last edited Feb 27, 2011 at 12:31 AM by robax, version 3


No comments yet.