Hello,
Ok, that makes it slightly more interesting...
[This was my first thought, but I think the second thought below will be more appropriate]
[1]
Do you have access to create another installation of DNN to a separate SQL database, or do you just have access to 1 SQL database where you have created your dev version of your site?
If you can create a completely separate install of DNN - I would do that. - From the fresh installation you can copy across the settings from your dev version. - This way if any mistakes occur then you still have your dev version as a backup.
To copy across your settings you can export all of the data from all of your modules by creating a portal template. - I've outlined this process in this post:
http://www.dnncreative.com/Forum/ta...fault.aspx
Video 2 of this tutorial also demonstrates
http://www.dnncreative.com/Tutorial...fault.aspx">how to create a portal template
I don't know how this will affect the repository module. I've checked the module and it does have the export data function, so hopefully it should work correctly.
[2]
Ok, I gave this a bit more thought and decided to run an experiment with a localhost installation - I would encourage you to do the same to follow the process through so that you fully understand it.
Installed DNN to a localhost installation using the domain name:
http://localhost/test
and this installation was stored in the 'test' folder
Added the repository module to a page, set it so that each user stores files in their own folder. - Added a doc.
I then added a portal alias of localhost/test2 (as outlined in the previous post)
and created a new folder called 'test 2'
I moved all of the files from the 'test' folder into the 'test 2' folder
and then created a new virtual website with a domain of
http://localhost/test2 which points to the 'test 2' folder
Upon navigating to
http://localhost/test2
DNN loads up with the new domain name and new location of files, everything appears to be working correctly.
But, of course the repository module links do not work.
To fix this, go to the Settings menu of the Repository Module
Scroll down to 'Folder for approved files'
D:\Web Design\DotNetNukeWebsiteTest\test\Portals\0\Repository
On these 3 folder URLs, change the URLs to point to the new folder location on your server, eg.
D:\Web Design\DotNetNukeWebsiteTest\test2\Portals\0\Repository
Click Update.
Everything should now be working correctly.
It's lucky that the repository constructs its URLs on the fly and takes the first portion of the URL from these settings, so you can specify any location you require.
I would test this for yourself first & make sure you create a backup of all of your files before attempting. - I have not tried this on a live website, but the localhost test seems to work ok.
Let me know how you get on,
Thanks,