• Okie dokie.

    Is it possible to salvage work already done on a WP2.1 installation?

    History
    I installed WP 2.1 on a brand new MYSQL database for someone with a Godaddy free (ad-supported) site. It worked fine until activating two plugins (Spam Karma 2.2r3 and Comment Timeout 1.0 beta 3) caused the .htaccess to be changed with the WordPress site breaking as a result. (See this for more info if needed.) It generates a 500 server error. The Admin dashboard however continues to function. The old html pages continue to work.

    Diagnosis
    Deactivating the plugins, and then additonally trying to remove the WordPress inserted lines in the htaccess didn’t resolve the problem.

    Proposed solution
    Attempt to use WP backup, delete current database, and start over with new installation on a new database.

    Questions on how to implement
    1. Under Manage > Backup it says “download an xml file”, but it doesn’t download anything in Mac Firefox or Safari, or Windoze Firefox or IE. It just spits out about a dozen lines of html links. Viewing source it shows an xml file. Can this be saved as a .xml in a text editor and used for restoring?
    2. If the xml file from #1 can be used, how and will it cause additional corruption?
    3. What do I need to do with the htaccess file to get the site to work?

    I’m an amateur at this stuff so help and simple step by step instructions will be most appreciated. Thanks!

Viewing 1 replies (of 1 total)
  • Thread Starter ciryaquen

    (@ciryaquen)

    Something is definitely wrong here.

    I’ve now done clean installations of WP 2.1 four times!!!
    * deleted and setup a new MYSQL database each time.
    * uploaded a freshly unzipped copy of WP 2.1 each time
    * deleted all .htaccess files and loaded a blank text file as .htaccess

    Using the default installation doing any one of the following things causes a blank page with a square and a ? to be displayed below the Godaddy ads.
    * turning on permalinks
    * changing the timezone
    * turning off “Attempt to notify any Weblogs linked to from the article (slows down posting.)”
    * turning on “WordPress should correct invalidly nested XHTML automatically”

    In other words trying to select anything other than the default options kills the blog. No plugins were even activated.

    I confirmed with Godaddy that the site has MYSQL 4.0.27 and PHP 4.3.11.

    Help please! Or give up on WP 2.1 and go back to WP 2.0.7?

Viewing 1 replies (of 1 total)
  • The topic ‘How to start over with WP 2.1 after it self-destructed?’ is closed to new replies.