RW Resources folder in site-path when publishing?

[teefers (Doug Bennett)]

As I told you in another post

Nubee question about replacing an old site

If you are using Apache for your webserver, RapidWeaver has a built-in editor in the publishing settings for something called the htaccess file. In the Apache htaccess file, you can use something called a redirect. So you can forward any requests for the old URLs to the new URLs. You should put together a spreadsheet “mapping” all the old URLs to what will be the new URLs (including the download links) Then simply create the htaccess rules

it’s very simple to do a redirect from an old URL (link) to a new URL address.

You can even redirect to an entirely different domain hosted at a different company in another country on the other side of the world. Most redirects are a single line.

Redirect 302 /DOWNLOADS/my-file.pdf /resources/downloads/my-file.pdf

Once you have tested the redirects you’re implementing and are sure they work simply change the 302 (temporary) to 301 (permanent).

You can even get more creative and use RewriteRule that would redirect all files with the same file name, from an old directory name to a new directory name, with a single RewriteRule.

RewriteRule ^DOWNLOADS/(.*)$ /resources/downloads/$1 [R=301,NC,L]

That rule would take every file request from an old directory named downloads and redirect it to the new directory resources/downloads, and return the 301 return code.

@Moshe

Have you published a site with RW, and did it include /resources/ in the path?

Almost every website that’s ever been published with RW8 has a resource folder. So that’s a yes by tens of thousands of sites.

It’s only for resources not in the general URL folks use to find and browse a site with. It’s no different than your current structure of having /DOWNLOADS/ in the pathname. In fact, it could be considered better practice and less confusing than using mixed case paths.