SITESUCKER TOO MANY HTTP REDIRECT ARCHIVE
SITESUCKER TOO MANY HTTP REDIRECT DOWNLOAD

if you have a page at /archive that should load archive.html, and there are also pages accessible at /archive/xyz, then you need a rule to make sure a request to /archive loads the HTML file, and doesn't try loading a directory index!).

SITESUCKER TOO MANY HTTP REDIRECT DOWNLOAD

You can preserve links to pages that are now also directories in the static download using another mod_rewrite rule (e.g.You can redirect links to /node (or whatever was configured as the 'front page' in Drupal) to / with another mod_rewrite rule.You can preserve Drupal pager functionality without having to modify the actual links in HTML files by setting DirectorySlash Off (otherwise Apache will inject an extra / in the URL and cause weird side effects), then setting up a specialized rewrite using mod_rewrite rules.Once you're finished getting all the files downloaded, there are some additional things you need to configure on the webserver level-in this case, Apache-to make sure that file paths and directories work properly on your now-static site. 3 - Make Drupal paths work using Apache rewrites To test things out, I point the domain for my site to the new server in my local /etc/hosts file, and visit the site.

SITESUCKER TOO MANY HTTP REDIRECT ARCHIVE

(If you have a slower or shared server and hundreds or thousands of pages on the site, you might not want to check this box-Ignoring the exclusions and the crawler delay can greatly increase the load on a slow or misconfigured webserver when crawling a Drupal site).Īfter the download completes, I zip up the archive for the site, transfer it to my static Apache server, and set up the virtualhost for the site like any other virtualhost. I change the following settings from the defaults to make the download go faster and result in a mostly-unmodified download of the site: SiteSucker lets you set options for a download (you can save your custom presets if you like), and then it gives a good overview of the entire download process: 2 - Download a verbatim copy of the site with SiteSuckerĬLI utilities like HTTrack and wget can be used to download a site, using a specific set of parameters to make sure the download is executed correctly, but since I only convert one or two sites per year, I like the easier interface provided by SiteSucker. The page above has some good guidelines, but basically, you need to make sure to all the 'dynamic' aspects of the site are disabled-turn off all forms, turn off modules that use AJAX requests (like Fivestar voting), turn off search (if it's using Solr or Drupal's built-in search), and make sure AJAX and exposed filters are disabled in all views on the site-a fully static site doesn't support this kind of functionality, and if you leave it in place, there will be a lot of broken functionality. 1 - Disable forms and any non-static-friendly modules I though I'd document my own workflow for converting typical Drupal 6 and 7 sites to static HTML to be served up on a simple Apache or Nginx web server without PHP, MySQL, or any other special software, since I do a few special things to preserve the original URL alias structure, keep CSS, JS and images in order, and make sure redirections still work properly. ), or the event for which the site was created has long since passed (e.g. The page references tools and techniques to take your dynamically-generated Drupal site and turn it into a static HTML site with all the right resources so you can put the site on mothballs.įrom time to time, one of Midwestern Mac's hosted sites is no longer updated (e.g.

has an excellent resource page to help you create a static archive of a Drupal site.

Sitesucker too many http redirect