Nov 112010

As the WordPress theme review process gets really strict about what WP functions are permissible in themes and what are not, it becomes more and more difficult for theme developers to support older versions of WordPress. Most developers have already taken the step to stop supporting anything older than version 3.0.

I have always been pro-backward compatibility and Suffusion works for any version of WP starting from 2.8. But with the complexity of code and the stringency of approval criteria rising, this will not be sustainable. As a result I have decided to phase out support for older versions of WordPress.

I will start by first removing any code that is specific to version 2.8, then remove 2.9 support. I would like to make this post a formal announcement of this decision. If you are a Suffusion user on a version of WP older than 3.0, now is a great time to upgrade. Version 3.0, which came out in early June has been stable for a while now and has some great features. If you haven’t upgraded you are missing out on a great number of goodies. And if the only reason you are not upgrading is because some plugins that you are using have not been written to work with 3.0, you should start looking for alternative plugins for the same task, or else you will run the risk of having a very inefficient system, or one where your theme and plugins will support different versions of WP.

With regards to version 3.6.8, I have already released version 3.6.9 with fixes for all the reported bugs in there. It has been approved, but not made live yet by the reviewers, so please sit tight.

Aug 102010

After a lot of delays and innumerable back-and-forth exchanges, a version of Suffusion has finally been approved – 3.6.3. This is essentially a combination of a large number of features and fixes, from release 3.5.8 through 3.6.3. If you look at the Change Log.txt file in the theme folder you will get an idea about how big the changes actually are:

  1. Bug Fixes
    There were quite a few bug fixes, actually:
    1. Fixed a bug that was displaying the “Comment form closed” message even if the settings were done to hide them. The slow approvals mean that questions get asked hundreds of times on the forum – this happened to be the top question over the last month.
    2. Fixed a minor problem with the style resets that I introduced in 3.5.6. This particular bug was causing Gallery items to spill over into a new line.
    3. The “Page of Posts” template was showing a NOTICE message with WordPress debugging turned on. I have fixed this.
    4. In my zeal to optimize code I had removed a bit too much in the “Now Reading” library page. The page was throwing up an error – that has now been fixed.
    5. Fixed a bug in the suffusion-tag-cloud short code. This was assigning an incorrect value to the number parameter.
      Note: You can use this short code in a text widget to display a tag cloud. It gives you a lot more control in terms of the number of tags you want to show and the sizes you want to set for each.
    6. Fixed a bug in the Custom Post Types section that was not saving post types with the correct index.
    7. Fixed a bug that was causing single quote characters in the post title to cause invalid markup.
    8. Fixed a bug in the “No Sidebars” template where the maximum width of the image was being set incorrectly.
    9. An incorrect control switch was being used to determine if custom font settings were to be used. This has been fixed.
      Note: If your fonts suddenly seem to have changed, go to Visual Effects → Body Font Settings and select “Custom Styles” for the first option and save.
    10. Fixed a couple of XHTML validation bugs. The first would occur if you have a gradient image selected for the header, and the second would occur if you had opted to use compression (GZip or minification) on the CSS files.
  2. New Features
    There were tons of new features added.
    1. New Widget Areas
      There are nine new widget areas. Technically there are five, but the fifth is a special kind:
      1. Widgets Above Header – This is in response to requests to be able to display ads above the header.
      2. Header Widgets – This, again, is in response to requests to be able to use the blank space near the blog header.
      3. Wide Sidebar (Top) – This is widget area that sits above both your sidebars if your sidebars are on the same side. Otherwise this is not shown. It is as wide as both your sidebars combined.
      4. Wide Sidebar (Bottom) – This is widget area that sits below both your sidebars if your sidebars are on the same side. Otherwise this is not shown. It is as wide as both your sidebars combined.
      5. Ad Hoc Widgets 1 to 5 – This is something new and quite interesting. There are 5 new widget areas called Ad Hoc Widgets 1, … Ad Hoc Widgets 5. You can add any widgets you please there. You can then invoke these widget areas from within your posts or pages, if you want. You have short codes to do this:
        [suffusion-widgets id='3']

        You can use any number from 1 to 5 for the id.

    2. As stated above, the short code to display ad hoc widgets, suffusion-widgets is new.
    3. There is a new page template for logging in, called “Log In”. You can use this template to create a login page for users. Mind you, this doesn’t tie up with the Meta Widget directly. You have to explicitly provide the link to users to log in.
    4. You can now customize the labels on your Comment form. Head over to Blog Features → Comment Settings to do so.
    5. There is a new Polish translation, thanks to Robert Maculewicz!
    6. JavaScript files are now added to the bottom of the page by default. You can change this by going to Blog Features → Site Optimization.
    7. Added capability to display text in multiple columns using short codes [suffusion-multic] and [suffusion-column]
    8. Added translation support for child themes.
    9. Added support for assigning menus to locations in the Appearance → Menus section of the admin panel. This comes with a change of behavior: if you assign a menu to the Top Navigation Bar and the Top Navigation Bar is hidden, it will still show up. Additionally if a menu is not assigned to a navigation bar in the Navigation Bar Setup options, but is assigned through the Menu administration page, the menu will show up.
  3. Modifications
    Some of the existing functionality has changed:
    1. Code Optimization
      This is yet another release where I have reworked the back-end. The impact this time, though, is not severe. I had noticed, as had quite a few users that the options panel had become quite sluggish. Of course, when you are looking at 400+ options loaded from a 6000 line file into JavaScript memory you are bound to have performance impacts. So I did a subtle split of the options menu and prevented it all from adding to the JS footprint. Earlier you had this:
      Previous Look

      Previous Look

      You now have this:
      New Look

      New Look

      I have essentially moved all the horizontal tabs into the side menu. The back-end is now noticeably quicker than what it was in the previous releases.
    2. I made minor CSS changes to the Minima skin. I will continue to tweak the style sheet in minor ways till I am convinced it looks good.
    3. I have switched off the “Comment form closed” message by default. Users who wanted to see the message will need to revisit the settings in Blog Features → Comment Settings.
    4. Code Housekeeping:
      1. Replaced occurrences of include(TEMPLATEPATH . '/searchform.php') with get_search_form(). This is as per the new approval process and it improves child theme support.
      2. Replaced occurrences of file includes with get_template_part(). This is as per the new approval process and it improves child theme support w.e.f. WP 3.0.
      3. Removed support for comments from WP versions older than 2.7. Suffusion anyway has been relying on at least 2.8 for widgets since a long time, so this code was redundant.
      4. Added call to new function comment_form() in comments.php. This is as per the new approval process, though it is quite counter-intuitive. I had to leave the old code in place, because there are still users who use WP 2.9 and for them the new function will not work.
      5. Moved licensing information to style.css file. This doesn’t impact you as an end-user.
      6. Enqueued all JavaScript file inclusions.
    5. Updated Brazilian Portuguese translation, thanks to Alcides Soares!
    6. Changed behavior to exclude posts from the static Featured Content section in the rest of the content on a page.

Hope you like this combined multi-release.

Jul 282010

A disclaimer
I would have posted this on WP’s official site if it allowed me to post, but since it doesn’t, I am publishing it on my own blog. This is meant as an appraisal of the new theme approval process on WordPress.

On 9th June 2010 WordPress made an announcement that it was expanding the theme review process. There was a call for volunteers to support theme reviews. This was indeed good news, particularly if you were a theme developer. For a long time Joseph Scott had been the sole approver of themes on WP, and though his work was impeccable and his reviews very good and accurate, if he was traveling or unwell or on holiday theme approvals tended to get delayed. This was by no means a deal-breaker, but having more people looking at themes definitely meant that things would get better.

Soon after the announcement a few things happened that were moves in the right direction:

  1. Quite a few folks signed up in response to Joseph’s post, so there are more volunteers now.
  2. A dedicated Trac project was setup for approvals.
  3. Every time a theme got submitted the corresponding Trac ticket got emailed to the theme author so that he/she could follow what was going on with his theme.
  4. There was much better focus on the quality of code in a theme. Actually the focus was more on writing code that didn’t generate “silent errors” or PHP NOTICE messages, but nonetheless adhering to this is something that keeps down the size of logs on your server.

But that is where the goodness stopped. One of the key things which I had hoped would be addressed, speed of approvals took a nosedive. To cite an example earlier when I submitted a theme version it would take around 1-3 days to get approved. It took 1 day if I submitted it on a weekday and typically 3 days if I submitted it on a Friday. In some cases if it was vacation time then the versions took about a week to 10 days to get approved, but this was more of an exception to the rule. Normally on a day you would see 2-3 versions of different themes getting approved, and on occasion the number of approvals even ran into double digits.

However, with the new experiment somewhere something went wrong. Now you have around 1 theme being approved in 2-3 days, which doesn’t seem right. To drive my point home, version 3.5.7 of Suffusion got approved on 10th July. Today is 28th July and only nine more versions of different themes have been approved (including a version of the WP default theme Twenty Ten). This is a far cry from how things happened earlier. I normally used to wait for about a week before pinging the folks to check the status of a version, so for 3.5.4 I sent out a message asking what was up, and this is what I received:

Thanks for the note.  Unfortunately there is currently a backlog of themes in the review queue.  We are working on it.  Themes are being reviewed in the order in which they were received.  Thank you for your continued patience.

I didn’t know at that time how much the backlog was or how much longer the next version of Suffusion would take for approval. I found out later how you can estimate the potential wait time. The backlog, as I know now, is well over 100 theme versions at present. So somehow adding more people slowed down the process.

The delay also brings in a bunch of associated problems. Currently if you have a theme version in the queue and you submit a new version, the older version gets deleted and the newer version goes to the back of the queue. So as a theme developer:

  1. If I have submitted a bug-fix for the theme 3 weeks back and that hasn’t been approved, how do I ensure that my users get the bug-fix? Distribute it from my site (unapproved)? Doesn’t sound safe.
  2. If I have submitted a version 3 weeks back with some bug-fixes, then I discover some more bugs in the submitted version what do I do with them? If I resubmit a new version I go to the bottom. So I add another month or so to something that has already been in for 3 weeks? Ouch. Incidentally I have had this happen to me quite often, most recently with version 3.5.8 and 3.5.9.
  3. If I choose not to submit the bug-fix for the older version but let the bugs be approved (these are niche bugs that cannot be caught in the approval process, mind you) and then I submit the new version, I am risking users staying with a buggy version for an indeterminate number of extra weeks.

So somehow this review process discourages active theme development, which I feel is counter-productive to the whole experiment.

How can the experiment be improved? I have a few suggestions:

  1. Improve targets. Set a target saying that each approver should aim to disposition a new theme for approval every weekday (or some such figure). If you have 10 approvers, this will take care of tackling 10 themes everyday and bring down the backlog much faster.
    I can almost hear people say, “What does he know?”, or “He is speaking like a consultant”, or “He is oversimplifying”. Well, I have been doing free support for Suffusion since late last September and that is how I keep my backlog down. Every morning I go through all outstanding support requests, take a crack at answering them if they haven’t been answered by someone else, then carry on with my regular job for the rest of the day. If a request comes in during the day, if I am not doing much then I respond to it (or if I think others can respond, I skip it). This has been a largely successful way of staying on top of things. I have responded to more than 3000 posts on my support forum at around 10 posts per day.
  2. Don’t de-prioritize existing themes in the queue upon newer submissions. I love putting out new functionality in the theme, and anyone with any experience whatsoever with Suffusion will agree with me in the fact what I provide is not just cosmetic, but hard features. Sometimes a new version is required to patch a bug. Getting pushed to the back of the queue is very off-putting, because it simply adds so much more in terms of wait time for approvals.
    This simply encourages parallel avenues of theme distribution because developers know that their work will not be approved soon on WP’s official site, so they distribute it from their site. And that is where they can start putting in stuff like tracking code etc into a theme. Mind you, quicker approvals will make this a non-issue, but the current wait of a few weeks is a bit too much.

As a concluding remark, the topic of this post and the issues in the post are not mission-critical and I am sure people have more interesting things to do. However I am sure that the free theme developers would be quite happy with these modifications, particularly since some of them invest a lot of energy in building their themes.

Jul 112010

Earlier today Suffusion obtained its 100th rating on This puts it it rather exclusive company – it is now the 5th theme to obtain this distinction. The four others to have reached this landmark before me are:

  1. Atahualpa – Really the inspiration behind Suffusion and in my opinion the gold-standard of theme customization, Atahualpa is way ahead on all statistical measures on WordPress: most downloads and most ratings. At the time of writing it has been rated a whopping 418 times on WordPress!!
  2. iNove – Another theme that has been around for quite a long time, iNove has been rated 193 times at the time of writing.
  3. Mystique – This is a really popular theme with WP users because of its catchy design. The only theme younger than Suffusion to have been rated more times than it, Mystique has 140 ratings at this point. Its current popularity will probably ensure that it will go over iNove in the near future.
  4. Thematic – It is no surprise that Thematic is the only free theme that has been in the top 15 popular themes since as long as I can remember, and that is very long! No other theme – Atahualpa, Mystique and iNove included has managed this distinction. Thematic is a very clean and well documented theme framework that most people swear by. If you are a theme developer, look at Thematic (and Hybrid) to see how to do it right. At present Thematic has been rated 111 times.

Though unlikely it is possible that I have missed a few here. So if you are aware of any other themes that should be here by all means let me know.

Thank you users, for using Suffusion and voting for it to let people know that you have liked it!

Jun 222010

I submitted version 3.5.4 on Sunday, before flying out to the UK. I see that WordPress has still not approved it, so I await the release patiently. This was a big release in terms of the number of fixes and enhancements, so without much ado here is the list:

  1. Optimization
    I did some optimization on multiple fronts:
    1. I introduced a new section under Blog Features called Site Optimization. Most optimization activities have been moved or added there.
    2. I have merged the contents of bgiframe.js with suffusion.js. This is to reduce the overall number of HTTP requests
    3. I have merged the contents of dbx.css with style.css, again, to reduce the overall number of HTTP requests.
    4. You now have options to choose GZip and minification at various levels. Mind you, different plugins can achieve this at various levels for you. In general the capability built into the theme is competent, but not all-encompassing. If you are using a plugin and are happy with it, by all means stick with it. But if you are not using a plugin or don’t want to use one or you don’t have , feel free to give this a shot. From what I have found out this does improve performance on Google Page Speed and on Yahoo YSlow. Feel free to disable the optimization if it doesn’t work well for you:
      1. You can GZip and / or minify the theme’s CSS files from the Blog Features → Site Optimization menu
      2. You can GZip the internal WordPress JavaScript files (like JQuery). Note that these files are already minified, so you don’t have to do anything on that front. Also note that the GZip process doesn’t apply to Suffusion’s JS files (like the JQuery Cycle script for featured content). This is due to a shortcoming in tying together WP’s inbuilt function wp_enqueue_script with the GZip capability. Plugins can still do this for you.
      3. You can also GZip your main content, all from the same Site Optimization section.
  2. WP 3.0 Retro-fixes
    WordPress changed a few things between its last RC version and the final release version. I took care of those in this release:
    1. WP renamed the support type for navigation menus from nav-menus to menus. Because of this the navigation menus seemed to not be working in version 3.5.3 with WP 3.0, while they worked for WP 3.0 RC and Beta versions.
    2. WP also renamed the function is_post_type to post_type_exists. This was causing custom taxonomies to not be associated with custom types in version 3.5.3 (again, this was working for the RC and Beta versions). I have addressed this too.
  3. More WP 3.0 Support
    I have added an option to “flatten” the navigation menus of WP 3.0 in the Navigation menus. Using this setting you will no longer see the menu names in the navigation bar. I have also included WP’s standard code to include feed URLs (this is internal and shouldn’t make a difference to you as a user).
  4. New Widget Areas
    I added two new widget areas: Sidebar 1 (Bottom) and Sidebar 2 (Bottom). These are respectively positioned below Sidebar 1 and Sidebar 2 and will be on the same side as the main sidebars. You can style these sidebars individually, so effectively you can have two sets of tabbed sidebars in the same column.
    As an aside the total number of widget areas in Suffusion is currently 10.
  5. New Action Hooks and Filter Hooks
    A lot of new hooks were added, both as action hooks and filter hooks. You can use these hooks to put in some fancy stuff either through the custom PHP method or through the child theme method. Here are the hooks:
    1. Action Hooks
      These have been added with respect to the sidebars. You can use these to put in some custom markup above your sidebars or between the sidebars or below them.
      1. suffusion_before_first_sidebar
      2. suffusion_between_first_sidebars
      3. suffusion_after_first_sidebar
      4. suffusion_before_second_sidebar
      5. suffusion_between_second_sidebars
      6. suffusion_after_second_sidebar
    2. Filter Hooks
      One filter hook has been added:
      1. suffusion_get_post_title_and_link – You can use this hook to append or prefix the post title with some other text. E.g. You can, as one user requested on the forum, have your own image before the post title, or as another user requested, put in a date in the list layout view. Currently the tile layout doesn’t have this hook, but it will have it in version 3.5.5.
  6. Miscellaneous Changes
    I fixed a small bug brought about by my use of the post_class function. This was causing attachment views to show up unstyled. Now they will get the post class. Another bug I fixed was related to the “Page of Posts” template. For some users this seemed to be ignoring the “Display All Posts” I also made minor modifications to the different layout files by adding global variables that indicate what kind of layout you are using – blog, tile or list. Again, this kind of a change doesn’t impact you, but it is useful if you are going to write your own templates. The last change I made was the addition of an option to disable the use of the body_class internal WP function, because apparently PHP 5.2 has some issues with it. Frankly, this wasn’t my problem to solve, but then again, such things have never prevented users from asking me to resolve their issues.

Now for the next release. I can say for sure about two new features in 3.5.5. One is a couple more widget areas (a lot of people have been asking for widget areas in the header). Another is the use of TimThumb with WP-MS, something that has been in my To-do bucket ever since I released BP support for the theme. As for more features, I need to see what I can fit in my timeline.

While it has been humorously suggested that I am a machine, and while a lot of users on the support forums make demands from me seriously assuming I am a machine I have to remind you what I mentioned at the start of the post: I am in London this week, hence my response times and development speed will be off. Also note that I am not in charge of approvals at WP, so please don’t keep posting questions asking when version 3.5.4 will be available – I have no visibility into that.

Jun 172010

After months of waiting and after a series of Beta versions and Release Candidates WP 3.0 finally came out today. I encourage all of you to upgrade your installations.

Why Should You Upgrade?

Version 3.0 is a significant release that has a lot of terrific features. Here are some:

  1. Menus
    This is arguably the most awaited feature of WordPress. This is  a huge relief for developers more than users as we don’t have to code our themes to provide you with a mechanism to select pages / categories / links to build the menu. As long as the themes offer basic WP 3.0 menu support you are good to go. You can build and structure your menus as and how you want with very little restrictions.
    Suffusion has supported native menus from version 3.5.0.
    It has been brought to my notice that WP pulled a little trick here. In the release version they changed a call ever so slightly, thereby making it seem like menus don’t work in Suffusion 3.5.3 (and a bunch of other themes that claim to support menus). To fix this:

    1. Open functions.php in your theme editor
    2. Search for the line that says add_theme_support(‘nav-menus’);
    3. Change that to say add_theme_support(‘menus’);

    That’s all.

  2. Integrated Multi-User Code
    With WP 3.0 the two branches of code, WP-MU (multi-user) and WP have been merged. You need to tweak a few settings to convert your site from a regular WP site to a WP-MS (multi-site) installation. You can start by creating a network.
    Suffusion can be used for WP-MS and can be made to work with BuddyPress too for a better experience.
  3. Custom Post Types and Custom Taxonomies
    The next big feature for folks wishing to use WordPress as a full-blown CMS is the concept of Custom Post Types and Custom Taxonomies. This offers limitless possibilities. If you have a site where you do reviews of books, movies and music, you can create custom post types for each of those, then associate custom taxonomies to them, like authors for books, actors and directors for movies and artists for music albums. In a theme that supports child themes you can suitably create your own templates for each of these post types and make them appear very different from the regular “blog” look.
    Suffusion added a plugin-like feature to let you define custom post types and taxonomies in version 3.5.3. This functionality will be enhanced in the next few releases.
  4. Native Support for Custom Header and Custom Background Images
    Now theme developers don’t have to code up a bunch of stuff to handle custom header images and background images. Of course, if you are like me you might still want to code up things – coding definitely gives you a lot of flexibility.
    Suffusion doesn’t support this feature at present, but it will, very soon. I couldn’t beat the WP 3.0 deadline, to be honest 🙂

Why Shouldn’t You Upgrade?

Simple answer – themes and plugins. Before you upgrade make sure that your theme is tested to work for the theme you are using. I am assuming that you are not necessarily a Suffusion user, so if you are using a theme that is not compatible and you upgrade, you will find yourself on a sticky wicket.

Another reason why you shouldn’t upgrade is if you have some indispensible plugin that is not tested on WP 3.0.

How Should You Upgrade?

If you don’t see an option on your admin Dashboard to upgrade, head over to Tools → Upgrade and then do the upgrade.

There is always the manual upgrade option, where you can download the zip file from WordPress, unzip it and overwrite everything apart from the wp-content folder.

What? No Suffusion News?

Come on! You cannot expect me to sign off without talking about the progress on Suffusion!

I have been busy the last week adding some optimization-specific stuff to Suffusion, like an ability to use GZip compression and minification on CSS and JavaScript. I have been largely successful in improving a lot of things, significantly bumping up the scores on Google Page Speed and Yahoo YSlow. Mind you, YSlow is quite hard to please – Yahoo’s own site scores a “B” grade on its performance test.

I have also been working on a ton of other stuff, small and big. Stay tuned – a new version will be submitted soon.

Jun 012010

Minutes after making my submission of version 3.5.1 I realized that there were some errors that had inadvertently crept in because I used the body_class() method. So I had to fix the errors and resubmit the theme, but as version 3.5.2. Now, I had already laid out plans for 3.5.3 before making these changes, so another feature found its way in. So here are the changes for 3.5.2:

  1. Support for Child Themes
    This was another of those long-time to-do activities that I finally got around to delivering. This was surprisingly easy to incorporate and I just had to make a handful of changes. You can now define child themes for Suffusion. This is very easy for you as well. Let us assume that you will create a child theme called “Son of Suffusion”. Here is what you will do:
    1. Create a folder called son-of-suffusion under wp-content/themes.
    2. Create a file called style.css in this folder. Put in these lines:
      Theme Name: Son of Suffusion
      Theme URI: http://your-theme-url
      Description: Child Theme based on Suffusion
      Version: 1.0.0
      Author: Your Name
      Author URI: http://your-url
      Template: suffusion
      @import url("../suffusion/style.css");
    3. The last line in comments, “Template: suffusion” is critical. It tells WP that your theme is based on Suffusion. Make sure that what you put in there is the directory where Suffusion resides.
    4. The first line after the comments is important if you want to use the Suffusion stylesheet. If you don’t have it, Suffusion’s styles will not be loaded.
    5. That’s all, really. You can add additional styles if you wish. This would be one way to not use the “Custom Styles” option. You can also add a functions.php and define your own PHP functions there. That would be one way to avoid using the “Custom PHP” functionality. Note the following:
      1. What you define in functions.php adds on to the existing functions in Suffusion’s functions.php file.
      2. Any other template file that you add overrides Suffusion’s templates. So if you create your own author.php file, that will take precedence over Suffusion’s author template. One very important use of child themes is if you want custom templates for custom purposes. E.g. You can create a file called category-16.php and define a special layout for your category with id 16. You can also create author-specific templates for WP 3.0. See WP’s template hierarchy for more details regarding how to add custom templates.
    6. Suffusion’s huge array of options will all be available to you using this method. Ensure that you keep the theme up-to-date.
  2. Bug fixes for some errors introduced by the body_class() function, for static pages. Of course, after submitting 3.5.2 I caught another of these errors for author pages, but I am not going to bother with another release before WP approves my current release.

That’s it for now. I guess 3.5.2 will be a significant release for you users because it will come armed with both BuddyPress support and Child Theme support. So just keep waiting for WP to approve, while I figure out how to make some more WP 3.0 functionality available to you.

May 282010

I submitted version 3.5.1 about a couple of hours back today, which is a pity because I believe I missed the bus for it being approved today, which is an even bigger pity since it will probably not be approved before Tuesday (1st June). Sad, because it has one HUGE feature.

  1. BuddyPress Compatibility
    After quite a few months of procrastination I finally bit the bullet and built full BuddyPress integration capabilities with the theme. It was not a difficult task thanks to the BP Template Pack plugin, but it took a really long time to implement. I had to go through a large number of files, check the layouts for each of those, modify all my stylesheets etc, because the output that I was getting was simply ugly. Also, the BP Template Pack plugin is still in its evolving stages, so there is a lack of consistency in the way it does its HTML markup.
    Mind you, you don’t need the BP Template Pack plugin to enable BP integration with Suffusion. This release takes care of that. Of course, you do need the BuddyPress plugin itself :-).
    As I mentioned, this was a very long exercise and I got a bit desperate towards the end last night. As a result some minute errors might have fallen through the cracks. Please feel free to post them on the support forum.
  2. Bug Fixes
    Surprisingly there were some unexpected bug fixes. I say unexpected because they came up in functionality that has existed for a long time.
    The first was in the “Page of Posts” template, where if you chose to display posts in the “List mode” the output came out wrong.
    The second was a 2-pronged bug in the image fetching function. The “Tiles mode” and the “Magazine layout” were not picking up an image defined as a thumbnail through WP’s native thumbnail feature. Plus under certain conditions TimThumb was not being invoked for resizing the images. I have fixed both of these. Note that if you are using WP’s native thumbnails you will not be able to resize them using TimThumb (I will have to investigate if it is possible to integrate TimThumb with native thumbnails)
    The third was in the Search results. I had never realized that the Search results were showing a date box and categories even for pages. Combined with the fact that I recently added some support for WP’s post_class() function, the net result was that the date was showing up for pages in search results in a really ugly manner.
    The fourth fix is for the static tabbed sidebar, where a div element within the custom tabs would automatically get hidden. Now it won’t.
  3. New Features
    I added a capability to disable the “date box” on the search results page. This will ensure that a page returned in a search result doesn’t look dramatically different from a post.
    I also added in the body_class() call to the body element of the HTML markup.

With this release I can lay serious claim to be able to support the multi-site capability of WP. If you weren’t aware, WP and WP-MU (Multi-user) are merged in version 3.0 of WP. So you can run WP in a single-site mode (default) or in multi-site (MS) from the same installation. Suffusion always worked fine with WP-MU, but BP integration had been a headache.

I still have to test out one tiny little to-do item – TimThumb integration with WP-MS, and I promise to do it soon.

This whole process of making the theme extract full mileage from WP 3.0 is getting very exciting. Let’s see what I can do with the remaining features.