By StrangeWork.com: After reading Jeff’s WordPress upgrade post I decided to take the plunge and upgrade my blog to WordPress 2.3. As always WordPress has made this process extremely easy. Simply follow their online instructions and you shouldn’t have a problem.
One small annoyance, which was changed a few versions ago, is the removal of the Post Preview Pane located at the bottom of the posts form. WordPress 2.3 does include a Preview >> link, but I hate opening new windows just to preview a post. Here is a quick hack to get the Post Preview Pane back:
Open up your post.php file from your wp-admin directory.
Navigate to approximately line 72 and find the following line of code:
include(‘edit-form-advanced.php’);
Directly underneath that line, add the following code:
?>
<div id=’preview’ class=’wrap’>
<h2 id=”preview-post”><?php _e(‘Post Preview (updated when post is saved)’); ?></h2>
<iframe src=”<?php echo clean_url(apply_filters(‘preview_post_link’, add_query_arg(‘preview’, ‘true’, get_permalink($post->ID)))); ?>” width=”100%” height=”600″ ></iframe>
</div>
<?php
Save your changes to post.php and upload. Easy as that!
WordPress 2.3 has added some really slick new features including native tag support, plugin update notifications, and a few new SEO URL updates. It appears all of my plugins ported over without issue, but be sure to check your plugins before upgrading.
I also have the dashboard bug that Jeff posted here. Apparently it has something to do with using Google Blogsearch rather than Technorati. I’ll see if I can find a hack to switch it back to Technorati, because that is a feature I’ve always enjoyed.
* UPDATE
I found the hack for incoming links.
If you want to get Technorati results back change:
“http://blogsearch.google.com/blogsearch_feeds?hl=en&scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:”
on lines 11 and 12 in index-extra.php to
“http://feeds.technorati.com/cosmos/rss/?url=”
and
“http://www.technorati.com/search/”
I recommend everyone take the plunge and get upgraded!
Related posts:
- How to Get More Blog Traffic: BlogRush.com
- How To: Move a WordPress Blog to a New Hosting Account
- How To: Setup Native Tagging Support in WordPress 2.3
- How To Increase Blog Traffic part 1: Google Webmaster Tools
- How To: Remove nofollow from WordPress Comments
Guess I spoke too soon as I received an error on my comment subscription plugin when I posted this. There is no upgrade available for it yet so I’m going to find a different subscription plugin that works with 2.3.
Found the hack for incoming links.
If you want to get Technorati results back change:
“http://blogsearch.google.com/blogsearch_feeds?hl=en&scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:”
on lines 11 and 12 in index-extra.php to
“http://feeds.technorati.com/cosmos/rss/?url=”
and
“http://www.technorati.com/search/”
It’s reassuring to know it’s a simple step. I just need to find some free non-workday time to do it!
Yeah it wasn’t bad at all. I would set aside about an hour from start to finish. I backed up everything before upgrading as well just to be safe!
Thanks brad for the Technorati replacement hack. Works like a charm.
for me, I’ll wait til a lot of plugins has been upgraded and bugs has been fixed before taking the plunge.
I’m waiting for 2.3 via Fantastico. Fantastico just makes it too painless to upgrade, and nothing breaks. (Knock on wood)
Yeah Fantastico is a thing of beauty, but I didn’t want to wait to try out the new features.
The latest upgrade causes the damn linkbacks to come from google blogsearch again. Guess I’ll have to reapply this hack each time I upgrade WordPress :(
Once again, this tip has come in handy. And I’ll comment on how great this tip is each time I have to change the damn file with every upgrade
Should you ad this exactly as you have it or turn around the opening and closing php tags. Sorry i am a newbie when it comes to this php stuff but i’m learing more and more each day.
?>
<iframe src=”ID)))); ?>” width=”100%” height=”600″ >
<?php
Thanks in advance
Travis
@Travis – yes add it exactly as I have it highlighted above. You are closing out the line above which is PHP code.