Typo official weblog

Guess what? We’re not dead, and we’re even working on Typo next minor release which should be 5.0.4.

Last week-end, we finally added tag administration, after integrating Cyril Mougel’s tag autocompletion. You can now edit tags, delete them, and you will soon be able to merge them.

We’ve also fixed some of the remaining bugs, leaving Typo with only 3 open bugs now. We now there’s still much to do, and we’ll run extensive tests to find remaining naughty bugs.

There is still lot to do and guess what ? You can even help us submitting patches (and tests, never forget tests).

Doc

We know how much our doc is outdated, and the next release will change this for 3 major docs:

• Typo user guide.
• Typo install guide.
• Typo theming guide.

Converters

If we had to find a single common point between our doc and our doc, it would certainly be not being up to date at all. Wordpress and Movable Type have evolved as we were evolving too, and converters were left aside since 4.0.

We now need to update these converters to reflect last Wordpress and Movale Type version, and allow people to switch from them to Typo. A migration doc should also be written.

Multiple users

Multiple users has been on our TODO list for a long time now, and is still slowly going its way. It will be made in 2 times : multiple users with profiles and grants, then per users settings for the whole blog.

More admin tweaking

I’m still unsatisfied with the current admin and plan to improve it a bit. I’ve asked a designer frend of mine to help make the current one cleaner while keeping it the way it is, which mostly implies CSS tweaks.

I also want the admin to be the simplest possible, following the Habari project path I really felt in love with in terms of usability.

And last but not least, more dashboard information.

Typo 5.0.3 “Don Mc Cullin” released on February 2008 the 24th is mostly a bugfix and refactoring release, going along with some improvements, everything leading slowly but surely to 5.1.

Less bugs, more speed

Honnestly, Typo has never been so fast and so bugless as well. We’ve rewriten most of the caching engine, and it’s now running flawlessly. Our effort to speed up the code has also been pursued and we can be proud of what we’re releasing.

Brand new editor

The blog editor has been rewriten too, to be more functionnal and user friendly. We’ve also switched the rich text editor from TinyMCE to FCKEditor for 4 important features :

• Fullscreen edition (kicks ass baby)
• Spellchecking
• Safari compatibility
• Impressive localization

More localisation

We’re continuing the localization effort to port Typo in your language. Default themes has been localized, and we now provide up to 8 languages :

• English (default)
• French
• German
• Italian
• Japanese
• Mexican Spanish
• Polish
• Romanian

Many thanks to all the translators. Currently, only French translation is really complete.

No gem?

We won’t provide you the habitual gem we used to. Rails app installer – formerly known as Typo installer – is brocken with Rails 2.0.2 and Typo instances installed this way just don’t work.

We hope you’ll enjoy Typo 5.0.3 as much as we enjoyed bringing it to you.

Download Typo 5.0.3 at Rubyforge

• English.
• French.
• German.
• Italian.
• Japanese.
• Romanian.

Choosing a version number for Typo has always been something difficult that may have seem curious or anarchic to some of you. What is the difference between a major and a minor version, why have we skipped major version 3 and did we go directly to 4.0 ? All that sort of questions you may have and never dared to ask. Or maybe you just don’t care and you’ll keep reading just to make fun of my English.

Why did we went from Typo 2.6.0 to Typo 4.0?

Ever heard of Typo3 PHP CMS? No? Now you know.

Why did you go from Typo 4.1.1 to 5.0?

Typo 5.0 came up with Ruby on Rails 2.0 which is, for many reasons, a really big version upgrade of our beloved framework. It may have been the most important Rails version migration of Typo’s life, and this justified the version number upgrade as well.

What is the difference between Typo 5.0.1 and Typo 5.1?

Typo 5.0.1 is a bugfix release to Typo 5.0. We’re going to deliver these bugfixes at regular times, every 2 or 3 months, or for special reasons :

• The release fixes some critical bugs that make the application crash.
• We’ve fixed a security breach that may compromise your blog or your server.
• We’ve fixed a huge amount of small but soooo ennoying bugs and want to release the new version before our due date.

The next stable version we plan to release is Typo 5.1, which will have some minor releases, 5.1.1, 5.1.2 and so on. It’s easy, isn’t it? Last but not least, minor versions (like 5.1.2) may add new cool small features here and there. It always comes as a surprise.

After releasing Typo 5.0, we’ve discovered a critical bug making Typo deleting itself when clearing the cache. This is now fixed, and we’re happy to announce the release of Typo 5.0.2. Typo 5.0.2 is mostly a bugfix release with some admin improvements. It also fixes a Rails bug on update_all making Typo unable to save sidebars config under pgsl and sqlite.

You can install or update the gem as well as download the archives from Rubyforge.

Following Typo 5.0 release, we’ve released early this morning a 5.0.1 bugfix release that fixes 2 majors bugs we’ve discovered last night.

The first one deals with the cache wipe being too agressive and sometimes wiping the whole blog directory. The second one with users listing crashing because users profile were not populated properly.

Typo 5.0 “Eugène Atget” finally finished after about 7 month of slacking making. This in an important release, stuffed with great new features, loads of fixes and an incredible amount of polish. This may sound like DHH introduction to Rails 2.0, and it does, because Typo 5.0 now runs with Ruby on Rails 2.0 and won’t run with anything else. That’s the reason of the major version change.

Before jumping into the breakdown of features, I’d just like to extend my deep gratitude towards everyone who helped make this release possible. From Piers who made this possible to the (hundreds of) contributors who got a patch applied to everyone on #typo who kept the spirit alive. You can all be mighty proud of the role you played. Cheers!

Why Eugène Atget ?

I’ve wanted to give our releases a name for a while now, but we needed to find a path we should follow from along the versions. Piers and I are both photographers, and most of the visible work on Typo has been done in Paris, which is a town Atget spent his life to picture. That’s the reason why his name came first when we had to choose one.

Sidebars removal

As we announced earlier, we’ve decided to move most of the sidebars plugins out of the trunk. There are many reasons why we think that, out of some basic functionnalities, sidebars should be third party softwares apart performances issues. We’ll continue to maintain these plugins anyway.

If you’re using one of the following plugins, be sure to install it, or your blog may explode with lots of nasty error messages.

• AIM presence
• Audioscrobbler
• Backpack
• Delicious
• Flickr
• 43 things
• 43 places
• Magnolia
• Recent comments
• Tada
• Upcoming
• Xbox

Plugins are now in our plugins repository, and installs like any rails plugin. Expect basic archives soon.

/path/to/typo$ ./script/plugins install http://svn.typosphere.org/typo/plugins/some-plugin

Code refactoring

The immerged part of the iceberg, but not the least one, most of the existing code has been rewriten. Typo was started when Rails was young, very young, and lots of things were added to the framework after we had to write them.

The result is impressive in terms of performances, and bug fixing as well.

Admin refactoring

Admin has been entirely revamped, twice, between 4.1 and 5.0, and we’re quite proud of how it works now.

The existing admin was the result of a scaffold during Typo early days, and even though some improvements has been done, many things were not as user friendly as they should have been. New admin now aims at giving a clear view on the information, and eased access to the most daily used functionnalities in your blogging life.

Simple and avanced admin

We now deliver the admin in 2 flavors, simple and advanced, because everybody doesn’t have the same need when it goes to blogging. We have also splitted the settings in 2 places, to separate basic and advanced settings.

More localisation

4.1 introduced Typo internationalization, but no one noticed it as it was hidden in the deep of environment.rb. You can now choose your prefered language from the settings. We hope the community to support the translation effort.

Comments moderation

Another hidden feature of 4.1 I think it’s important to mention here is default comment moderation. This is a stone in the build of a better discussion management.

Theme editor

A theme editor was a missing piece in Typo admin, and it’s now filled with a basic, but usable editor. For now it allows you to edit your layout and stylesheet. Views editing will come later.

Dashboard

We’ve also added a dashboard we plan to improve with time. It aims at giving you a view on the latests activity on your Typo blog.

Solving SEO issues

For long time now, Typo has been a pain to search engine optimisation, mostly because most pages, out of single posts, had the same meta title and description. That thing we never noticed before had nasty effects when melted with Google duplicate content algorythm, which even led some blogs to be banned from index. Expect some more improvement in a near future.

New themes

Azure which has been Typo default theme for a while now has been removed from the core and won’t be supported anymore. Standard issue is now our new default theme, and we have introduced Dirtylicious as well. Scribbish has been kept for backward compatibility as many blogs are using it, starting Piers.

Both themes were built above Scribbish markup and are thus hatom compliant.

Typo themes garden

I know this should be a community matter, and it may not have its place on a release note, however I think it’s important enough to mention it. Every theme listed on dev 411 Typo theme viewer has been updated to support Typo 5.0, and updated themes are already avaliable.

We do think having a usable themes and plugins park is important, and too many themes were only Typo 2.6.0 compatible. That’s the reason why we did the themes migration while finishing Typo 5.0, and we plan to port even more non Typo themes in a near futur.

And now ?

Now, we’re going to have some rest while you’re migrating and giving your first feedbacks. We already have a new roadmap to Typo 5.1, which contains

• Atom Publishing Protocol.
• Admin feeds.
• Working to make the admin interface talk APP.
• Themes with helpers.
• Customizing the Feedback state machine so different spam protection engines can use different states.
• Add users grants
• OpenID consumption.
• If we really have to, multiblogging…
• Even more admin improvement.
• Doc, doc and even more doc.
• Plugin manager tool.

We hope you’ll enjoy this release as much as we enjoyed making it.

We’re late at releasing Typo 5. By 4 days as far as I know. Don’t think we’ve just been slacking, that’s false. Truth is out there used to say agent Mulder, and I do agree with him tonight. I’ve always been a Danna Scully fan. So what ?

We had to choose either to release an unready buggy Typo 5.0 just to keep the delays, or let you wait a few more days and give you a cool nice Xmas present. We choosed the latter without hesitation. So what happened ?

I’ve spent my sunday evening and my monday morning porting the 117 themes from dev411 Typo themes viewer to the new version. Most of them were 2.6.0 compliant and they all needed some tweaks. That’s done, and they will be online in time for the release. I’m now porting a bunch of 63 wordpress themes. Feel free to help, it’s easy, all you need is some HTML knowledge, a text editor, Firefox and Firebug.

We’ve added 2 new themes as default, replacing the old Azure with Standard Issue, and adding Dirtylicious as a secondary theme. Scribbish stays in the default themes for backward compatibility. There are too many blogs using it as a default theme to just remove it that way. We’ve also added a theme editor, useful for people who don’t want to mess with FTP to edit their templates.

We’ve been bumping into some huge issues with Rails 2.0 caching and Piers is working on it to get everything fine before we release. There are still a few minor bugs left now, and they will be fixed as well before release time.

That’s all folks, stay tuned.

After last week Rails 2.0, Typo 5.0 is soon to be released. As this is a major change, we have decided to change the default theme and to let you decide what you want as a default theme.

Standard issue

View Standard Issue in action.

Dirtylicious

View Dirtylicious in action.

Abstract

View Abstract in action.

Rambling Soul

View Rambling Soul in action.

Nautica

View Nautica in action.