Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Would using the No Blog Clients plug-in cause problems if you use Feedburner with your own domain?

    In General I think the best advice is to rarely upgrade WordPress. Have an automated backup system that backs up your WordPress directory, images (probably separately), and database. A cron job shell script using mysqldump and tar works well. Have the backup run daily or weekly, depending on how active your blog is. But don’t upgrade WordPress.

    When your site is hacked (if it ever is … it’s less common than you’d expect from reading the hysterical blog and forum posts on the internet), you recreate the database from the MySQL dump and then do a clean install of WordPress with the latest version (*this* is the upgrade) and copy your various settings and images in. WordPress will update the database schema if necessary. And you’re done. Not much harder than doing a WordPress upgrade, but you only have to do it every two or three years, if ever.

    What is the Apache config fix, specifically? In other words, what lines would I add to or edit in Apache config? Or is it RTFM? If so, which M? What topic in the M?

    I installed wp-super-cache last night and woke up to find a dead site (the admin worked though), with this in the logs:

    [Sat Oct 18 01:45:35 2008] [alert] [client 55.55.55.55] /usr/local/www/data/pathtomysite/wp/wp-content/cache/.htaccess: ExpiresActive not allowed here

Viewing 2 replies - 1 through 2 (of 2 total)