Group items tagged

Yesterday had a quick look at podPress, the premier plugin for podcasting. It has a small incompatibility with the new Post Revisions feature introduced in WordPress 2.6. PodPress seems to be in the middle of a large update. I’ve used the “experimental” version (8.9) of the plugin and emailed the proposed fix to the authors, however for the more impatient here is the patch: view plaincopy to clipboardprintfunction post_edit($post_id) {      GLOBAL $post;      if($this->justposted) {          return;      }      $this->justposted = true;        if ( isset($_POST['post_ID']) && (int) $_POST['post_ID'] )          $post_id = (int) $_POST['post_ID'];        $this->settings_item_save($post_id, $_POST);  }   function post_edit($post_id) { GLOBAL $post; if($this->justposted) { return; } $this->justposted = true; if ( isset($_POST['post_ID']) && (int) $_POST['post_ID'] ) $post_id = (int) $_POST['post_ID']; $this->settings_item_save($post_id, $_POST); } It goes in podpress/podpress_admin_class.php, around line 51. What it does is to make sure the custom post meta fields used by podPress are attached to the actual Post, not one of the revisions.

Like the title says, upgrading WordPress isn’t as difficult as you might think. As long as you don’t have a lot of “core upgrades” i.e. direct edits to WordPress core files, it shouldn’t take you more than a few minutes. In this tutorial I’ll show you how in 3-4 simple steps. Take a full backup first Get the latest version of WordPress Overwrite core files Run the database upgrade script (if necessary) This tutorial will be going over everything manually. You can use things like Fantastico and those “automatic upgrade” scripts at your own risk. It may be a good idea to read this guide on installing WordPress first, but not necessary.

After upgrading WordPress from version 2.0.5 to 2.3.3, I did some experimenting with the “post autosave” feature. The autosave feature uses some crafty ajax to automagically save your post every 2 minutes (120 seconds by default). Below the post-editing field, you will notice a line of text that displays the time of the most recent autosave, similar to the following:

How to change the time-interval for the WordPress Autosave feature While experimenting with the autosave feature for this post, I discovered how easy it is to change the default autosave time interval. In WordPress 2.3 (and probably 2.2 and 2.1), open the wp-includes/script-loader.php and edit the instance of 120 (seconds) to something more appropriate. Don’t get too crazy though, or you might get a nasty email from your host. Here is how the interval-setting code appears on line #43: 'autosaveInterval' => apply_filters('autosave_interval', '120'),