The other day I installed the Nofollow Reciprocity plugin… and Bang! – another plugin conflict saw the light of day: On multipage posts, exactly at the second page the TOC boxes got entirely messed up.
Since I do not really use the multipage feature, I only noticed today, while working on, and testing,1 new TOC Boxes features. It took me a while to figure out that there is no bug in the TOC Boxes code, but a conflict stemming from somewhere else. Once I realized this though, it wasn’t hard to guess where the conflict comes from. After deactivating “Nofollow Reciprocity”, everything went back to normal.
- Aye, I test all the way long while I develop! 😉 [↩]
A minor update of Sliding Notes is out.
The release provides a workaround for a weird cross-browser issue on some themes, like the one reported by Magnus.
Download it as usually at wordpress.org.
Download it as usual at wordpress.org.
This article is sort-of an antithesis to a post called “Why developers should pick WordPress?“. While that post does make some good points pro WordPress, I’d like to show why it is not the whole story.
The Main Arguments Dissected
The mentioned article summarizes the most common pro WordPress arguments:
- It has prominent users (even governmental).
- It is more popular than its competition.
- It is in high (and growing) demand.
- It has a large (and cool) community.
- It is easy to learn.
A minor update of my TOC Boxes plugin is out. Besides fixing some small glitch, it adds the CSS class toc-anchor to the generated named anchors.
These anchors are inserted into the post to serve as link targets for links in the TOC box, and are (usually) invisible. The change mainly affects themes with unusual CSS styling for anchors in general, such as mentioned in my discussion with Daniel Nautré.
I’m writing this article in response to a question I’ve got recently, the answer to which I believe will be of general interest.
And the question is:
How to make automatically collapsed TOC boxes.
At the same time, I’ve corrected an “impurity” in the assignment of CSS classes, where the “collapsible” was attached to the title, instead the widget itself. Please change your CSS clauses Read more >>
According to feedback I’ve received, viewing the Widget Voodoo Configuration Tutorial was apparently problematic. I’m not even sure if anybody at all could watch the screencast, except myself. (I’m afraid that could well have been the case, though only view people complained, compared to the number of visitors.)
While the reasons for the issue remain a mystery, I decided to move the screencast away from googlecode, where I used to host it before.
Dear visitors, I’ll ask you for a favor. Please drop me a note whether you can watch the screencast or not. Thank you for your help.
The recent “Shadowchaser Release” of Sliding Notes brought – among other features – compatibility with the “Shadowbox JS” plugin.
I investigated the issue, and I’ve found out some interesting things.
- Anything that uses the Shadowbox.js script [↩]
I’m writing this post with a clear sense of pride about having chosen CSS selectors as “configuration syntax” for Widget Voodoo. The power and flexibility of the approach over other other, more limitting approaches is amazing.
Thank to this power, it was a “piece of cake” to resolve a help request on how to collapse al widgets at oncel I’ve got recently.