If your WordPress-powered site includes a blog as a component, rather than the main function, you can opt to put blog posts and archives (category/tag/date/author) into their own subdirectory (such as “blog”).
Here’s a list of 5 features that have gone missing in WordPress 2.5:
If you’ve been keeping up with WordPress 2.5, you probably know the intuitive drag-and-drop sidebar assembly of WordPress 2.2/2.3 has been replaced with a more cluttered method of widget administration, involving a dropdown to select the sidebar you want to work with (see screenshot).
At first glance this seems like a step backwards, but I came across a post called “In defense of the WordPress 2.5 widget panel” that makes a very good point:
If you’re into photoblogging, check this out:
When you have the Monotone theme set up on your blog, it will take the first photo attached to each post and place that image prominently at the top, with the post text and comments below.
Simple enough. But what’s unique about this theme is that for each post page, Monotone changes the colors on the page to match the colors in the photo! A very cool method for creating an eye-pleasing visual atmosphere for your photoblog.
Check out the Monotone demo to see it for yourself.
The theme isn’t yet available for download, but should be in a few days.
July 2010 Update: WordPress MU has been incorporated into WordPress 3.0 and later, so some of these differences are no longer relevant.
Although WordPress and WordPress MU share somewhere around 95% of the same code, there are many more differences between the two than just multi-blog support. Here’s a thorough analysis:
Here are 7 useful tips related to WordPress’s “Write Post” page.
This morning, the WordPress Development blog published a WordPress 2.5 sneak-peak that highlights some new features and changes in WordPress’s administration back-end (specifically, with regards to the Dashboard, admin navigation, the Write pages, and the Manage pages).
This potential problem is applicable to those using the following, which is probably quite a few people:
- Firefox with the highly popular Adblock or Adblock Plus extensions
- WordPress with the visual editor enabled
As part of its functionality, Adblock inserts a tab next to Flash objects, etc. to make blocking that object as easy as a couple clicks.
The problem is, Adblock will insert the HTML code for this tab into the visual editor for a WordPress post that includes Flash.
And who wants code like this in their posts?
If you’ve ever tried to insert code into a WordPress post, one of the following has probably happened to you:
- Your HTML code was rendered as such.
- WordPress stripped the code from the post entirely.
- WordPress turned "straight quotes" into “curly quotes” — not good if you want your users copying/pasting code from your blog!
Here’s how to get around these annoying problem and make the code show as-is: