Support » Fixing WordPress » Best practices to shut down and archive a WordPress blog

  • Resolved jefgodesky

    (@jefgodesky)


    I have an old WordPress blog that, at its height, got a good bit of attention. I haven’t written it in about a year, and I want to start a new blog, but not before this one has been given the send-off it deserves. Too many people link to it and use it for me to just let it disappear. By the same token, I don’t want to keep using the resources of an active site.

    What are the best practices for shutting down a WordPress blog? I’m running an old version (2.3.3), but I can upgrade if that’s what it takes. I’d like to be able to:

    (1) At the very least, shut off comments for everything.
    (2) It would be nice if I could generate static HTML pages, so that the archives don’t put any strain on a database.

    Do any tools exist to do this kind of thing?

    Thanks,
    Jason Godesky

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jefgodesky

    (@jefgodesky)

    1. I edited my themes to eliminate all dynamic material (closed comments, blocked registration, took off search, etc.)
    2. I used HTTrack to create a static HTML mirror (I would have preferred wget mirror as Otto42 suggests but I don’t have a Unix machine)
    3. I uploaded the archive to a subdirectory
    4. I updated my .htaccess to:
      RewriteEngine On
      RewriteCond %{HTTP_HOST} ^anthropik.com
      RewriteRule (.*) http://tobyspeople.com/anthropik/$1 [R=301,L]
    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I used HTTrack to create a static HTML mirror (I would have preferred wget mirror as Otto42 suggests but I don’t have a Unix machine)

    wget exists for Windows.

    http://gnuwin32.sourceforge.net/packages/wget.htm

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Best practices to shut down and archive a WordPress blog’ is closed to new replies.