After releasing Typo 5.4.3, we realized something we actually knew for a while. If we wanted Typo to spread more, we had to make it prettier, easier to install and easier to use. That may sound obvious, but we were working with a quite old product, having legacy feature we didn’t need, but, for some reason, we kept release after release, trying to work around instead of just dumping them. If we wanted to make Typo better, we first had to make it smaller. Dead obvious once again.
Being the fourth of the Willy Ronis series, that version is the first going towards simplification: less useless feature, simpler, better interface, and lighter memory footprint.
Typo now comes with a new, easier to use setup that suppresses needed initial configuration. Just provide an email and a blog title, and you’re done. This setup is the first stone in refreshing Typo installation process.
Previous admin refresh was not very satisfying, and we needed to rework it. Instead of trying to play the webdesigners, which none of us is, we used Jquery UI for the graphic part, and focused on Typo interface instead. The result is, for now, quite satisfying, even though we know we still can improve it.
IPs and pattern blacklist has been completely removed. With Akismet and real time blacklist (RBL), Typo already provided 2 simple ways to fight against spam. Blacklisting IPs and patterns was a very advanced feature, which is definitely not a blogware job. If people want to do that type of filtering, they have many way to do it, using intrusion detection systems (IDS), Apache mod_security, or even packet filtering such as Linux Netfilter.
For ages, Typo provided a full iTunes metadata support for podcast publishers. We’ve completely removed them since it was useless for 99.99% of us. Typo still supports enclosure (files attached to a blog post, appearing in the RSS feed but not on the post itself) though.
Instead of SQL stored sessions, we’re back to plain old cookie sessions. Sessions table was never emptied and this was part of Typo heavy memory footprint.
We’ve also resolved a bunch of bugs as well:
Issue 152: fix poor email grammar.
Issue 148: fixes a bug that prevents admin to edit a user without providing his password.
Issue 160: 404 error on the lightbox loading.gif and closelabel.gif.
Issue 155: after deleting an image, the file page is loaded.
Issue 143: publishing posts in the future didn’t work unless you manually unpublishes them.
If you’re still wondering whether or not you should upgrande, give our demo site a try first.