Please use the support forum for any questions you might have.
I have completed adding the finishing touches to the official plugin for the Suffusion BuddyPress Pack, to be distributed from the WordPress site. I am currently waiting for access to the SVN repository at WordPress so that I can upload the plugin. Once I have the access the plugin should be readily available. You will be able to search for it from your administration panel at Plugins → Add New by searching.
The plugin has come along quite nicely. I have also bundled in it the support for the BuddyPress Album+ plugin. In future iterations I will add support for a few more third party plugins, assuming they allow their templates to be overridden by the theme.
Note that for the plugin to work you must have at least version 3.6.9 of Suffusion, which is the current version.
Once the plugin is officially released I will let you know.
Before I begin about this release, I would first like to apologize to all people whose layouts broke due to the last release. As it turns out I had not tested certain configurations involving the static Tabbed Sidebar, which resulted in all people using this feature having their sites become train-wrecks. Disabling the Tabbed Sidebar would have fixed the issue for all affected people, but there was no way you as a user could have known that.
Anyway, this release is a bug-fix release and there are no new features. Here are the fixes:
- Layout bugs
- The biggest issue – wonky layouts upon activation of the Tabbed Sidebar – has been fixed. There is one exception – if you are using IE6 (yes, that fossil) and you have the Tabbed Sidebar on and your Tabbed Sidebar is on the left side and you have at least one sidebar on the left site, then your left sidebar will render incorrectly on IE6 (only on IE6). I spent some time trying to figure this out, but gave up because I had to get this release out early and this particular combination has an extremely low probability of occurring. Otherwise I have hopefully resolved all issues on all browsers regarding this mishap.
- The Widget Area Below Header was not spanning the full width of the wrapper and was showing a blank space on the side.
- The Widget Area Above Footer was overlapping the right sidebar if the sidebar was longer than the content.
- The No Sidebars template was showing up with empty space on the side.
- In the “Tiles” layout excerpt images were becoming very tiny because the widths were computing incorrectly.
- If you had defined more than one WP 3.0 Menu, each menu item was getting repeated multiple times in the navigation bar. This has been fixed too.
- There was a bug that was preventing the post footer from appearing in the archive view (front page, category, date archive, tag etc). So if you had Tags or “Posted By” at the bottom of a post, that wasn’t being displayed. This now works.
- There was a very old bug where the excerpt title in the “Tiles” layout where the header of excerpts wasn’t reading the alignment setting correctly. Instead it was borrowing the alignment of Magazine excerpts.
One point I would like to highlight – often when you upgrade your theme it apparently breaks your layout, while in truth there is nothing wrong with it. In such cases try out a few very simple things. First and foremost, clean out your browser’s cache and reload your page. Second, if you have a caching plugin make sure that you rebuild its cache, otherwise it will serve content that is not current.
- At some point in the last 3 releases the Google Translator widget stopped working. I have no idea why, since I haven’t changed anything there. If you were looking for this feature to work I encourage you to look for some free plugin to help you there.
- At some point in the last few months the Fade / delay effect on the navigation menu stopped working. Again, I have no idea why. Since this is a very low impact issue I didn’t spend an excruciating amount of time trying to resolve this.
Another aspect I wanted to highlight was regarding my comment in my previous post, about “Rolled up menus”. A few users had difficulty understanding the concept, so I thought I will explain it here. To create a new dummy node:
- Go to Appearance → Menus and open up your menu.
- Create a new menu item using a Custom Link.
- For the URL specify #. Make sure you delete the “http://” that sits there by default
- For the Label put in whatever you want to name your root node.
- Add to Menu
- Once added, move this item to the top of the list.
- Now, indent every other item under this top item. This way each other node is a child of your newly created root. Remember to indent – this is important.
- That’s it. Since you have set the URL to be “#” Suffusion knows that it shouldn’t open any page for it. All other items are listed as children of this new node.
That’s it for this release. I am hoping this will smooth over the rough edges of 3.6.8. I will keep subsequent releases smaller in scope, though, quite frankly I don’t foresee anything being so large in scope.
Over the next few weeks I will focus on building a proper plugin for Suffusion and BP compatibility, assuming that the support queue for 3.6.9 isn’t huge.
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.
After what seems like ages, here is a new version of Suffusion. As already mentioned, this has been a very very code-intensive release because of the nature of the changes.
These are the main changes in this release:
- New Features
The following were added in this release:
- Fluid Width – By far the biggest change in Suffusion since the inclusion of options in the very second release. This change required me to overhaul the HTML structure of the theme and always put the content before the sidebars, then do massive amounts of testing. While I put in every bit of effort required to get this working as per expectations, if you find something that is not working as you expect, please let me know. I will be very happy to fix it.
- Improved Menus – In any other release this would have been the prima donna. But as it stands, this has been relegated to second position. Now you have even better control of your navigation menus, in terms of the number of options you can pick from:
- Include all, ignoring next option
- Include selections from the next option
- Exclude all, ignoring next option (New)
- Exclude selections from the next option (New)
The new options can be better understood in context of some major code reengineering. Earlier I had a very comprehensive menu-building code, that worked very intuitively. This behavior was different from WP’s default behavior. However the old code created an insane number of queries, particularly if your menu was big.
In this release I have removed all my self-created code and resorted to using WP’s inbuilt functions –
wp_nav_menu. his significantly reduces the number of queries and the load on your server.
As a tip, if you want to completely remove pages/categories/links from your menu, use the “Exclude all, ignoring next option” setting instead of “Include selections from the next option”. This is much more optimal in terms of code.
- You can now get rid of the HTML title that shows up when you hover over your navigation menu. Visit Blog Features → Main Navigation Bar Setup → “Title” attribute upon hovering over navigation bar.
- There was no styling available for the HTML elements
fieldset. CSS declarations have been added for them.
- Removed Features
The following features have been removed:
- I have removed the “rolled-up” setting for WP 3.0 menus as it is redundant. If you want to create a rolled-up menu you can automatically create a base node in the menu and add the rest of your menu under it.
- I have also removed the option to not use
body_classWP function to generate classes for your body. This removal was essential because the
body_classfunction is essential to the style setup for the theme.
- Bug Fixes
The following bugs were fixed:
- A fix has been included for a severe bug that was causing page templates to max out at a width of 600px. The bug was caused by incorrectly applying filters to the sidebars and templates.
- The following navigation menu-related bugs have been fixed:
- Selected navigation bar items (Pages, Categories and WP 3.0 menus) were not getting highlighted in the Minima skin.
- Selected navigation bar items for WP 3.0 menus were not getting highlighted across any skin.
- The values set for highlighting in Visual Effects → Theme Skinning were not being accurately reflected.
- The following BuddyPress-related bugs have been fixed:
- In various BP screens, if something was selected from a drop-down list (like filters, or sort criteria), nothing was happening. The correct AJAX calls for this have been included.
- The Create Profile and Edit Profile pages in BP were not rendering properly. This has been fixed.
- Messages in the inbox etc. were not being styled properly. This has been addressed.
- There was a bug in the List Layout style, which was offsetting the posts by 1 if all posts were not being displayed. In other words, the top post was not being displayed, and if there were N+1 posts in all and each page was to display N posts, the second page was showing an error. This has been rectified.
- Links in featured content were not getting the right color. Again, this has been fixed.
- There was an error in the
charsetsyntax in header.php, style.php and rounded-corners.php. This wasn’t impacting anything as such, but it has been rectified nonetheless.
- In the options pages if you put in 0 as a value for some dimensions it wasn’t being read correctly. I have changed the code to handle this.
- The comments section has been revamped to look better and to facilitate better styling. There is now a custom callback function invoked from there.
- As per the theme review guidelines I had to change the credit link at the bottom. It now just links to the Suffusion home page and not my home page.
- Somewhat whimsically I have changed the default font from Arial to Trebuchet. You can however switch back to Trebuchet if you want, from the Visual Effects → Body Font Customization options.
- You now will not see any version tag appended to JS files included by the theme.
- The Spanish and French translations have been updated. Thanks to David for his modifications of the French translation!
I will soon update the Suffusion BP Pack so that you can make use of the new changes to the core theme. I will keep you posted.
After slogging very hard the last 3 weeks I managed to get all the changes I was hoping to include in place for version 3.6.7 last night. Making use of the illusion of an extra hour from daylight savings I went ahead and tried to submit the theme to WordPress.
But as I tried to submit it I hit a snag. I kept getting a message that said:
Error 413: Request Entity Too Large
No matter what I tried and from which browser and machine, the error did not change. It is highly likely that the WP servers had a configuration change in the back-end. I did post out a message to the theme reviewers asking them as to why this is happening. After all the file is just marginally larger than the previous versions and I have never had this problem earlier. Let’s see what they say.
As I mentioned earlier, the primary features of this release were a reworking of the navigation bar code, a fundamental change to the HTML markup and a set of options for fluid/flexible width. In addition there have been a number of BuddyPress-related style changes. I will release a new version of the Suffusion BuddyPress Pack when this version of Suffusion gets approved.
I will post a detailed change log once the theme is approved.
This is a follow-up to my previous post. I wrote earlier that I was incorporating fluid-width options into Suffusion. Over the past couple of weeks I have managed to work a good bit on this and I am happy to say that I have managed to get the markup rearranged, and I started full-fledged work on incorporating fluid width into the theme today.
You might be wondering what I mean when I say “get the markup rearranged”. To explain, with a fixed-width setting I can define my layout this way:
<div id='sidebar-1'>…</div> <div id='sidebar-2'>…</div> <div id='main-content'>…</div>
This would render my page showing the first sidebar, then the second sidebar and then the main content – in other words, it represents a layout with 2 left sidebars. The code would change depending on the layout. So if I wanted a single left and a single right sidebar, my markup would become:
<div id='sidebar-1'>…</div> <div id='main-content'>…</div> <div id='sidebar-2'>…</div>
This works pretty easily and well with fixed-width layouts because each column has a pre-defined width. However with fluid width there are significant problems in this approach. Typically fluid width layouts would mean that the sidebars have pre-defined widths in pixels, but the main-content column takes up the remaining available space. Naturally, when you have the main-content appearing before a sidebar, the challenges become significant.
The fix for this is to use what is referred to as the CSS Holy Grail. Actually the Holy Grail is for a fluid-width central column and fixed width sidebars, but the markup and CSS for it can be extended to fixed width layouts as well. Using this approach you will really have just one markup for all layouts:
<div id='main-content'>…</div> <div id='sidebar-1'>…</div> <div id='sidebar-2'>…</div>
You can then use the CSS properties
right to control where you want to show what. This approach is recommended by experts because:
- You can change your layout, but your content will always remain the same. So depending on your layout your CSS changes, not your HTML.
- This has the added benefit of being SEO-friendly, because your main content is closer to the beginning of your document. Particularly in cases where you have a long sidebar, this is a great benefit.
Porting this approach to a fixed-width setting, however was a huge challenge. Just think about it – I had to test all the following configurations for the changed markup:
- General layout:
- No sidebars
- Single left sidebar
- Single right sidebar
- Single left, single right sidebars
- Double left sidebars
- Double right sidebars
- Page templates for each of the 6 configurations above
- In each of the configurations above I had to factor in situations where you would have tabbed widgets, wide sidebars etc.
All in all this amounts to more than 50 different configurations. To add to the complexity, it would have been a great world if Internet Explorer was well-behaved. Instead, for each of the 50+ configurations above, I had to tear my hair out figuring out what works for IE6.
Anyway, this part of the challenge has been overcome. I am working on now putting in fluid width components into the layout. This has its own set of challenges. I had never imagined how easy fixed width has been so far. In changing the code I am now realizing how ingrained the fixed widths are into different elements of the layout. I had a lot of widths running off the main-content column’s width. Again, our favorite IE6 and Microsoft’s proprietary “expressions” are causing me a lot of grief.
Stay tuned – I will hopefully have the new release out very soon.
This is the longest I have gone between releases of Suffusion and unfortunately the current release is significantly more complex than the previous ones, hence version 3.6.7 is still a few weeks away from release.
A general fact of any software development cycle is that the more complex the software the longer the development cycle. As things stand today Suffusion is quite complex under the hood. As a result when I try to make a foundational change to the theme, it is a very very arduous exercise. Such changes were much easier to make when the theme was simpler. That is the difference between foundational changes and add-on changes: add-on changes are still easy to do given the theme’s modular structuring, which is why I can add new sidebars etc without breaking a sweat (actually adding sidebars is not that easy, but it still is much easier than what I am doing right now). There are two major changes I am working on at present:
- A revamped approach to navigation menus – I was never happy with the way WP handled its functions
wp_list_pagesetc. I felt that their concepts of “include” and “exclude” were slightly messy and I tried to build a fool-proof system for building menus myself. The net result:
- I was successful because I achieved what I had set out to do. Including and excluding items worked as advertised.
- I ended up introducing some rather undesirable inefficiencies in the code. The menu-bar code worked well, but to work the way I had envisioned it required to do a lot more queries in the back-end system. For users who had a large number of pages etc, the menus generated at least 100 extra database queries.
- Some plugins refused to cooperate with the menu code.
- Some features like highlighting the correct page etc were notoriously hard to implement.
So in this release I decided to fall back on WP’s standard functions instead of my enhanced ones. The result is that menus will not work the way I think they should (which shouldn’t really concern you – I am but one individual), but they will work the way WP thinks they should.
The change is complex because it required me to change all my menu code, test for pages, categories, links and WP 3.0 menus, fix all style-related problems and what not. Luckily though, this is a piece that I have finished implementing.
- An option for fluid width – This is a more cataclysmic change. It involves revamping the entire HTML markup and a humongous amount of implementation and testing. This piece is taking a lot of time to finish implementing, let alone get into full-blown testing.
Adding to the implementation complexity are some major changes on the personal front for me, like an upcoming move from the US to Canada and you can see why this release has been taking time.
The light at the end of the tunnel, though, is that once this release is done, you can do pretty much anything with the theme layout. At that point I can focus on the funky features I had promised in the birthday post of Suffusion.
Over the past several weeks I have been finding it very difficult to provide support for Suffusion. It is becoming increasingly difficult for me to keep up with my day job, theme development, support and most importantly, my life.
With immediate effect I am formally announcing a reduction in the support I provide for the theme. For folks familiar with the forums, there are 3 categories where you can post topics at present: Bug Reports, Support Requests and Translations. From now on, I will only respond to questions where I believe my explicit inputs are required, like a genuine bug report, or some specific support topics.
All questions of the following sort will be generally ignored by me (others might choose to offer solutions, though, and I might occasionally respond to such queries):
- How to integrate plugin X with the theme (which file to edit etc.).
- Most questions regarding why your layout is broken. I say “most” because there are times when the layout being broken is truly because of a bug, but in 90% of the cases it is due to a user putting in improper HTML.
- Any question on adding support for a feature will be ignored. For example, allowing Flash-based headers, ability to load images through the theme options etc.
- Questions asking “What will happen if I upgrade the theme? Will I lose my changes?” This question has been answered literally hundreds of times at several places.
- Sending me a PM asking for a solution will be ignored. And sending me an email asking for a solution will be ignored too. The forum exists so that people can share information, so sending me a PM or email defeats the purpose of the forum. As things stand today I anyway redirect users to post on the forum if they send me a PM or email, so it is not like you will lose out on any support by this official announcement.
The forum has had several thousand posts in the last one year and a lot of questions have been answered there. But what had been originally set up as a means to genuinely help people out has now become a free-for-all, with a lot of people rushing in to cut corners on development costs by piling on the free support offered here. I am finally taking a stand here – if you need a complex requirement for your site, please hire a developer and get him/her to customize the theme for you.
What you can do to speed up things on your side are the following:
- I encourage searching the forum and finding things out for yourself. As mentioned, several thousand posts exist in the forum and a very high likelihood exists that something has been answered.
- The software is released as open-source for a reason: so that you can read and modify source code if you really need to do something not offered by the theme.
- Without a trace of hubris I will state that the theme is extremely customizable, more than several premium themes. In addition, for people happy about writing code it offers you full support for child themes. Both of these combined let you customize the theme as per your will. Make use of these facts – they will make life a lot easier for you.
At this point I would like to extend my deepest gratitude to Connie, Dark_Fox28, Colin and other folks who have been tirelessly volunteering with support issues. If I do happen to meet any of you, lunch/dinner is on me.
I will continue to publish tutorials every now and then on how to maximize your output with Suffusion, and I will continue to put out new releases (albeit at a much slower pace), but please don’t expect anything more than that from me. It is quite depressing to receive 60+ support requests when you are on vacation for 2 days, when you know that you are already handing out software for free that would have taken people thousands of dollars to develop.
Update: This post has moved to a new location. In this post I highlight the short codes you get with Suffusion, in addition to providing an insight into how you can use short codes in general.