creating a top-level path for pages in a container

I’ve got a large number of files that were in the top level of an old web site, and I’d like to keep them there in the new MODx site so they can still be found on the new site. However, I’d prefer not to put them in the root container because there’s such a large number that it’ll clutter up the tree listing.

I have friendly URL paths turned on, which I need for several reasons. I tried putting all these top-level pages in a container, but of course that made them appear under a directory with the container name or alias. So I tried setting the alias to ".". This would make the refs show up as /./page.html, which is the same as /page.html. However, MODx can’t seem to find the files referenced as /index.php?q=./page.html even though it can find them in general with the reference /index.php?q=alias/page.html for alphanumeric aliases.

Any thoughts?

I don’t use FURL paths, but I do use FURLs. The difference is - ALL my aliases look like they’re in the root. Which is fine by me.

So unless you need FURL paths for some other reason, turning them off should allow you to have your docs appear to be in the root.

I need friendly URL paths because I’ve imported a large number of similar directories, the pages of which have the same names. If I imported them with different random aliases, then I wouldn’t know how to redirect the old URL to get the page in its current location. (There are too many to do this by hand.)

I tweaked the import code (which ought to be modified to do this in the distribution IMHO) so that if friendly URL paths are turned on, the code assigns the filename to be the alias instead of adding a random extension. Now there’s a deterministic way of redirecting old URLs to the new equivalent URL.