Skip to content

Daily Archives: January 2nd, 2012

How to turn off post revisions in WordPress 3.3

Did you just update to WordPress 3.3 only to find that post revisions have returned even though you previously engineered some way to turn them off?

Don’t worry, I can help – but, first, some background and chatter.

Way back in 2008 WordPress added Revisions to its core features, and the feature persists today in the newly released version 3.3.

This is the amount of WP revisions I can create in a single week of editing if left unawares.

Revisions captures every published iteration of a post you are working on, so that if you republish with some minor changes you still have the prior version available to roll back to, if necessary.

This feature can be helpful if you make a lot of major changes to your work, or if you are on a multi-author blog and need to occasionally reverse someone’s edits.

It can also be detrimental, or plain old annoying.

The revisions feature nearly destroyed Crushing Krisis. Because, you see, my managing editor is an OCD Godzilla that lives inside my abdomen and due to his influence I have been known to spend my spare time making literally hundreds of tiny edits to spelling and spacing across the million-plus words of this site. Each edit I published spawned a new post number in a new post ID. My database ballooned by thousands of lines, I was using more RAM on my server, and legacy posts and pages linked by their post IDs were suddenly appearing at new permalinks!

There have been plugins to turn Revisions off, but when a new version of WP debuts sometimes those plugins don’t work right away. That’s why I am sharing the manual way to turn off Revisions.

This involves editing core WP files. You do so at your own risk. I am not a WP developer, and I cannot provide support to you if you hobble or destroy your blog. Unlike a plugin, this will not still work after a reinstall or upgrade of WP, so when you move to WP 3.3.1 you need to do it again.

Ready?

  1. In your root directory you have a file called “wp-config.php.” Save a copy of it elsewhere in case you mess things up terribly.
  2. Open wp-config.php and scroll down. At some point you should see a comment that reads “/* Stop editing */” – we will insert our new code just above that.
  3. Insert this code:
    /* Disable Revisions Feature */
    define('WP_POST_REVISIONS', false );
    If you would rather just limit the revisions that get saved, change as follows:
    /* Limit Revisions Feature (by number of revisions) */
    define('WP_POST_REVISIONS',6);
  4. While you are here, you could also choose to add a line to define how frequently you would like WP to make single autosaves of your posts, which frequently saves my ass in the case of a browser crash. That code is:
    /* Set Auto-Save Timing (in seconds) */
    define( 'AUTOSAVE_INTERVAL', 300 );
  5. Voila! Though WP will still inform you of your revision number in your posts table, it is no longer saving revisions.

Keep in mind, you do still have a number of revisions in your MySQL database, sitting around doing nothing like some vestigial appendix-like organ in your body that may or may not cause a later explosion.

(If you are me, that number of revisions is 250 in the one hour since you installed WP3.3. Yes, I literally make that many edits to CK in an hour. OCD Godzilla is a terrifying beast.)

To do away with them you simply need to delete all of the rows in your post table identified as revisions. Any time you directly edit your MySQL is potentially bad mojo, so I am not going to specifically advocate doing that. However, if you have backed up your DB and know what you are doing, visit WP Recipes for the simple one-line SQL query that will wipe out your revisions.

I hope this helped you! Personally, I get completely frantic when WP updates and one of my old plugins stops working to provide (or, in this case, block) a feature I rely on.

#MusicMonday: “Try To Sleep” – Low

I hear newly released music via a four-point scale of acquisition.

1. Appointment. I know I love an artist. I know their LP is coming out. I pre-order it.

2. Recognition. I’m aware of an artist, who I might even like, or I hear a song on the radio that I enjoy. I see their name on a release schedule or in a review. I pick up their newest stuff.

3. Guided. A trusted source or a plurality of untrusted sources recommend an artist or album. Alternately, I hear the song enough times to be interested (which, given my lack of radio-listening or television watching, is pretty rare).

4. Acquisition. I am looking for new music in bulk to hear/review and pick an LP based on non-arbitrary factors like reviews by people I trust, how good the third song is, and how cool the LP cover looks.

Low is an example of a band who has moved up the strata year by year. They are presently somewhere around 1.5 on the scale.

It started with Low’s album The Great Destroyer. I had vaguely heard of the band, but though they were shoegaze or slowcore or something else that bores me to tears, so had avoided them until that point (i.e., they failed the #3 test). However, The Great Destroyer had a fantastic name and album cover (#4 sometimes saves me from snobbery in #3),  so I picked it up and wound up loving it. It was a little slow and gazey, but it also featured distinct counter-melodies and witty lyrics.

Fast forward five years, a period in which I picked up no further Low releases. Midway through 2011 I saw Low’s name on the LP C’mon and picked it up purely out of curiosity. Would it sound like Destroyer, or was that merely a catchy outlier?

“Try To Sleep” is the first track and lead single from that album, and without a doubt one of my ten favorites songs of 2011.

I forget what I was doing when I first heard this song, but I remember making a mad dash for my iPod to see who was singing it so I could rate it five stars. I was surprised that it was Low – while it’s only a minor modification on their typical sparseness, it’s also incredibly pretty. Continue reading ›