I’ve just upgraded my main two blogs, and have already tried the two features I’ve been waiting for:
- fully integrated widgets Starting with this release, widgets will be a standard part of the WordPress distribution, included in the core source code instead of being a separate plugin. Many recent WordPress themes support widgets already, and it is indeed a very easy way to manage sidebars of your blog. Since I’ve been doing my sidebars manually, it seems to be a perfect opportunity for me to migrate over and document the process in a form of a separate how-to post. Stay tuned!
- safer activation for plugins: a sandbox approachIf you ever installed more than 10 plugins on a single blog, you’ve probably been there already: you download a plugin, place it in the right directory, click activate in your administration panel, and it breaks your whole blog – nothing works, not even the administration panel itself. The only way out of this is to either remove the plugin files through SSH/FTP or disable its activation in WordPress database manually (phpMyAdmin or something like this). Neither of these methods are simple enough to be used by someone who doesn’t know much about WordPress.
This new release introduces a sandbox approach: all plugins are verified against fatal errors upon their activation, and unless they work safely enough (don’t break your whole blog), they are not activated. You get a nice error message explaining the situation should you come across a nasty plugin like this.
It took me only a few minutes to set up a fatal error scenario, and I must say: this feature is a great time saver on top of being a great plugin installation safeguard.
There’s a many more changes apart from these two, like full Atom 1.0 support – I just don’t use them as much and perhaps need to do a bit of reading/learning myself since too many things have changed in this version.
If you want to learn more, it’s best for you to read the great 10 Things You Should Know About WordPress 2.2 post at Technosailor. As always, Aaron Brazell has provided a great review of the most juicy features to be found in this WordPress release.
That’s all I wanted to tell for the moment. If you haven’t done so yet, wait no more – just go download WordPress 2.2 and upgrade, it’s definitely worth it!
Steve Smith has just announced that the FeedBurner plugin he had developed a few years ago and had been supporting ever since is now officially adopted by FeedBuner, and is supported under a FeedBurner FeedSmith name.
Here is a download link: FeedBurner FeedSmith 2.2
Installation instructions for the new plugin can be found on the FeedBurner: WordPress Quick Start page, however there’s a couple of steps they had missed, so I just wanted to post them here for the time being (I’ve also sent emails to FeedBurner about these, so with any luck they’ll be mentioned in the Quick Start guide soon enough):
1) Make sure you disable your old FeedBurner plugin before putting the new one into your WordPress plugins directory
If you don’t do this, there will be a conflict of plugins declarations, and you will have to FTP to your hosting and delete the old plugin file form WordPress directory manually in order to fix this conflict.
2) In FeedSmith, you don’t have to generate FeedBurner-specific feed redirect anymore. Instead, all your feeds will be redirected to FeedBurner by default. This means two things:
- you need to change the Original Feed back to its default in your FeedBurner feed options (log into your FeedBurner account, pick your feed, click Edit Feed Details…)
- you need to clean up your .htaccess file. Just find a line in your .htaccess (it will be in the root directory of your WordPress installation) which looks like this, and delete it:
RewriteRule ^feedburner_879394/?$ /feed/ [R,L]
That’s about it! I’ve just updated the plugin on one of my blogs, and will do it on the rest in the next few hours. If you need help with upgrading it, please feel free to ask!
It’s about time I start explaining how to combine great plugins publicly available to get the best results with your blog. Thinking about it, I’ve decided to start a series of posts on the plugins I think you’ll greatly benefit from. Starting today, every week I will talk about some new plugin. At a weekly rate, I think we’ve got at least 2 months of exciting plugins to be discovered!
What is one of the most important things about blogs? Why, sharing the content, of course! If you’re struggling to find an easy way for your visitors to share your posts with others – look no more. Sociable is a great plugin that will help you give your visitors an option of sharing posts through almost any well-known social bookmarking website (61 website is supported as of Sociable 2.0).
How it works
After each post of yours, you will see a toolbar similar to this:
When you hover your mouse pointer over a particular icon, it is shown in vivid colours and you get a pop-up note with the name of the website, like this:
When someone clicks one of these icons, a relevant social bookmarking website opens with a standard page for sharing a link to your post with others. If visitor is not logged in in a particular service, then username and password will be asked first. Login and sharing pages vary in their design and complexity, but Sociable takes care of the most important part of sharing links: it automatically generates URLs understood by social bookmarking websites, so that whenever a sharing page opens, it already has the proper URL of your post.
Once you upload plugin into your WordPress plugins directory (Sociable has all its files in a separate directory), simply activate it from the Plugins management panel of your WordPress Admin section. After this, in Admin’s Options you’ll see a Sociable tab with configurable sections:
1) Websites to be represented on Sociable toolbar
Out of a menu of many sites, which looks like this:
… you’ll be able to select only the websites you would like to be offered.
As you can see from this illustration, you can simply tick the websites you like. Also, as the instruction suggests, you can drag-and-drop options to achieve the perfect order of icons to be shown on your Sociable toolbar.
2) Text to introduce the Sociable toolbar.
You can type any phrase you like (and yes, there’s a default one too) – whatever you think will motivate most your visitors to bookmark your posts.
3) Sociable visibility options
This is a group of tickbox options at the bottom of the screen, which allows you to precisely limit the visibility of Sociable plugin. For instance, that’s the place to disable Sociable for your main page or archives pages. My personal preference is to show Sociable toolbar for posts and pages with useful content only, so I disable the front page and archives options:
I think that’s all you need to know about this plugin. It’s definitely one of the must have plugins in my opinion. Give it a try and I’m sure you won’t regret it!
- Official page of the Sociable plugin
- Sociable 2.0 download (02-02-2007 release)
- Sociable 2.0 interview with Peter Harkins
Hi everyone, and welcome to our new website!
As some of you can guess, it’s a slight modification of a rather popular Nonzero Red theme. Well, it’s not red anymore – that’s one thing for sure.
I like this new theme much more than previous template, and its flexible design will make adding new features a lot easier.
Well, it’s been two days since WordPress 2.1.3 and 2.0.10 security updates were released, and I’ve just upgraded the WP engine behind PerfectBlogger. It is recommended that all users of WordPress 2.x apply the relevant update. For WP 2.1, it’s WordPress 2.1.3 release, for 2.0 it’s 2.0.10.
Here’s the usual upgrade scenario:
- Download the latest WP version from WordPress downloads page
- Make a full backup of the current WordPress directory of your blog
- Make a full database backup (you should have such an option in your website hosting panel, or you can backup MySQL database manually if you have shell access to your web server)
- Unpack the downloaded WP archive and overwrite files of your blog’s WordPress with the new ones
- Verify as much as you can that everything works
It is important to always make backups. Even if you think you know what you’re doing, backup anyway – just in case.
Also, do plan for an immediate verification of the upgrade as it’s better to discover possible errors yourself than wait for your visitors to tell you (that is, if they can tell you given the severity of some upgrade errors – sometimes they can’t open your blog at all, and so won’t be able to submit a feedback form or leave a comment).
If you don’t want to download the whole archive with the latest release of WordPress, you can always follow the example of Mark Jaquith.
Just use the files and lists he generates for almost every WordPress release to only replace what’s really changed between latest WordPress versions. For this round of upgrades, please read Mark’s post on the WordPress 2.1.3 upgrade.
Good luck with your upgrades!
If you remember, WordPress 2.1 have introduced a built-in support for static frontpages. It caused some confusion initially, cause plugins which used to provide this functionality, stopped working completely. However, one you discover the feature, it’s very easy to use it.
There is one small problem though: is_home() function will not work for such static frontpages. To work around, you can use a plugin called is_frontpage. Here’s how its author, Martijn Stegink, describes it:
Version 2.1 of WordPress introduced native support for a static frontpage, which only has been supported by plugins before. When using this option however, the is_home function doesn’t work. This is because is_home is supposed to return true for the “blog” home page, where your most recent posts show up, not the “front” home page. An is_frontpage function is not available yet.
Therefore I whipped together this small plugin, called is_frontpage. Just download the plugin drop the file in your plugin folder, activate the plugin through the admin interface and the is_frontpage function is available to you. Use it just like the is_home function. It returns true if you’re at the frontpage you set, otherwise it returns false.
Taken from: Bos89.nl blog
If you still haven’t taken time to upgrade from WordPress 2.1.1 to WordPress 2.1.2 – do this right now! You can read the official explanation on the WordPress blog, but the bottom line is that WordPress 2.1.1 downloads have been altered by a hacker, and therefore may contain a security exploit.
To make sure you’re secure, it is advised that you download and install WordPress 2.1.2.
Note: this only affects users of the WordPress 2.1.1 build, any other WordPress 2.x version was not infected.
pS: if you need help with upgrading your version of WordPress, feel free to leave a comment to this post and I’ll be sure to contact you by email.
Since upgrading to WordPress 2.1, I’ve finally switched back to using the built-in posts editor. One of the reasons for doing this was that I’ve found the options I so needed – text justification and HTML code cleanup – available through the advanced editor options panel.
Pressing Shift+Alt+V in Firefox or Alt+V in Internet Explorer transforms your Standard Editor panel:
… into something like this:
As you can see, there’s quite a few more options available, namely:
- paragraph formattion options (address, preformatted text, headings)
- underline your text
- full justification
- color selector for your text
- paste options for plain text and MS Word
- messy HTML code cleanup
- custom character button (charmap which allows you to click and insert any special character)
With all these options, there really is no reason to search for a better visual editor anymore. TinyMCE, which is the engine behind it, fits WordPress 2.1 like a glove, and makes editing your posts and pages a real pleasure.
It’s been a bit over two weeks since the release of the long awaited WordPress 2.1, codenamed Ella, and although I had upgraded one of my blogs the very next day when it became available, it’s only now that I finally have some time to post about it.
First of all, please go and read the official announcement of WordPress 2.1. Once you learn all the new features, you will immediately know whether it’s worth upgrading or not.
If you have WordPress 2.0.5 and anything below it – don’t even waste your time: it is time to upgrade! Get at least version 2.0.7, although in most cases you should be okay just jumping up to 2.1.
There are many wonderful features in 2.1, but I personally like the following ones:
- Autosave - an AJAX-powered feature to save you from losing any of your ingenious posts again. Quite often, having typed a page or two of text, you lose your text if your browser crashes or something else interferes before you hit the Save button – so this Autosave feature is a real saver (pun intended).
- New visual editor for posts and pages – a much better looking editor which has a different tabbed interface for easier switching between post and its HTML code and also includes a spell-checker. It pleases me a lot that all the dialog windows appear normally in Firefox 2 now, cause they definitely were buggy in WordPress 2.0.7.
- Admin area rework – it works much faster, thanks to more AJAX code and a cleaner CSS.
- Upload manager – for a much easier uploading and management of your media files
Hope I got you interested in at least giving it a try? Although if you haven’t done this by now, there’s hardly anything to convince you. As a last resort kind of a thing, I offer you a 10 Things You Should Know About WordPress 2.1 by Aaron Brazell at Technosailor. His article gives a great introduction to new features, and I think you will benefit from it even if you think you know enough.
Yet another update of WordPress has been posted yesterday: WordPress 2.0.7.
Here is what the WordPress official blog has to say:
Recently a bug in certain versions of PHP came to our attention that could cause a security vulnerability in your blog. We’re able to work around it fairly easily, so we’ve decided to release 2.0.7 to fix the PHP security problem and the Feedburner issue that was in 2.0.6.
Here are the changes which the above comment mentions:
- Security fix for wp_unregister_GLOBALS() to work around the zend_hash_del_key_or_index bug in PHP 4 versions less than 4.4.3 and PHP 5 versions less than 5.1.4 with register_globals set to “On.”
- Feeds now properly serve 304 Not Modified headers instead of mismatched 200/304 headers (a.k.a. the FeedBurner bug).
For a full list of changes since 2.0.6, please have a look at the original post with WordPress 2.0.7 announcement.
You can't be too secure, and with this in mind I've just updated both my WordPress-based blogs and strongly suggest you do the same.