You can't really change where mojoPortal stores the files, but if you want the old url to work in addition to the new one, you could create a virtual directory named "documents" below the root of your site and point it to the physical folder at /Data/Sites/1/documents/

Hope that helps,

Joe

If it's a question of SEO in maintaining that root position, what I would personally do is move the "root" documents to the new documents directory, and in IIS put in 301 redirects for each of those files that have moved. That way you have a roadmap toward consistency and don't have to maintain legacy file locations. Going forward the webmaster should use /documents exclusively.

Since it sounds like you're in the preliminary planning stages of your implementation, I'll give you another tip that would have helped us out when we were at that stage. Rather than using:

www.mysite.com/Data/Sites/1/documents/file.pdf

You may want to consider using:

www.mysite.com/Data/Sites/1/media/documents/file.pdf

The reason for this is that non-Admin users who are given access to upload files in the editors will be shown the file tree starting from Data/sites/[site]/media, so they wouldn't be able to see/replace files located in Data/sites/[site]/documents.

Because of this, we've recently been going through a major reconfiguration of our files to move everything under the media folders so we can begin decentralizing maintenance of our sites. Once we're finished with this reconfiguration, we will turn on the "ForceAdminsToUseMediaFolder" key in user.config so file access through the sites will be consistent for all site editors.

If I could go back in time, I would have turned on that key from the very start!

I hope that helps,
Jamie

I think you should do these redirects at the IIS level. I believe the mojoPortal 301 redirect manager is only meant to work with renamed mojoPortal pages.

It took me awhile to figure out how to do redirects in IIS too. The easiest way to do it is through IIS Manager. In IIS Manager, drill down into your site in the left pane. Here, you can select a directory and then in the right pane select HTTP Redirect and make it point to where you want with a Status code of Permanent (301). This is how you should set up your /documents directory redirect.

It's a little more complicated to interactively set up redirects for individual files. When you browse to the location that holds your files to be redirected, in the left pane right-click on the folder with your files in it, and select Switch to Content View. In the right pane you'll see the contents of the folder. In the right pane, find a file to be redirected, and right-click on it, then select Switch to Features View. At the top of the right pane you'll see the file's name and icon displayed, indicating that you are operating on that file. Now you can select HTTP Redirect, and it will set up a redirect just for that selected file.

Behind the scenes, what this process does is to create redirect entries in a web.config file that look like this:

<location path="MyFile.pdf">
        <system.webServer>
            <httpRedirect enabled="true" destination="http://www.mysite.com/Data/sites/1/media/MyFile.pdf" httpResponseStatus="Permanent" />
        </system.webServer>
    </location>

For folders and files that are outside of the mojoPortal root (like your /documents directory), this is not an issue since it will creat a new standalone web.config file. However, I think your root documents may actually be sitting in the root of your mojoPortal site. If this is the case, the redirect entries will be added to the big web.config file for your site. This is not a problem per se, but you'll just need to be aware that these entries are customizations, and they will have to be manually migrated to the newly delivered web.config file each time you upgrade mojoPortal.

I hope that helps.
Jamie