Having Typo sending emails using Gmail (or any other TLS enabled SMTP)

By default, neither Typo nor Ruby On Rails can send emails using a TLS enabled server. To have Typo sending you new posts and comments notification, or even your admin password, you’ll have to tweak it a little bit. Here’s a step by step tutorial.

First, you’ll have to install the ActionMail Optional TLS plugin. From your Typo directory, just run:

<typo:code> ./script/plugin install http://github.com/collectiveidea/actionmaileroptional_tls </typo:code>

Easy as pie isn’t it?

Then, in your config/environment.rb, replace the following lines:

<typo:code lang=’ruby’> begin mailsettings = YAML.load(File.read(“#{RAILSROOT}/config/mail.yml”))

ActionMailer::Base.deliverymethod = mailsettings[‘method’] ActionMailer::Base.serversettings = mailsettings[‘settings’] rescue # Fall back to using sendmail by default ActionMailer::Base.delivery_method = :sendmail end </typo:code>


<typo:code lang=’ruby’> ActionMailer::Base.smtpsettings = { :tls => true, :address => “smtp.gmail.com”, :port => “587”, :domain => “YOURDOMAIN”, :authentication => :plain, :username => “GOOGLEUSERNAME”, :password => “GOOGLEPASSWORD” } </typo:code>

Restart your application. Enjoy having Typo sending you emails from Gmail.

Published on 16/04/2010 at 21h07 by Frédéric de Villamil, tags

Release of Typo 5.4.4

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.

Typo 5.4.4

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:

The main reason why we’ve released that new version so early was because of a bug in the visual editor, losing posts content at saving time. Editors are very difficult to test since they rely on Javascript. However, we plan to add some Watir tests in a near future.

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.

Published on 05/04/2010 at 19h26 by Frédéric de Villamil, tags , , ,

Poll : shall we remove Typo enclosure and iTunes related feature

Once again, we’re back on our favorite code editor, working on a better, lighter Typo. Which means removing useless, or at least unused parts first.

Maybe you didn’t know about it, but Typo has native podcast publishing feature. Just fill in some settings, attach your article a MP3 and you’re done. We’ve been wondering for a while if you, Typo users, were actually using those feature, or if they were just a useless burden on our favorite weblog engine. If we realize no one actually use them, we’ll eventually drop them from the next release. The only question will be wether or not we should leave backward compatibility, and that’s the reason why we’ve setup that quick poll.

In the meanwhile, we’ll be working on improving our attachments and media library, but that’s a another feature we’ll discuss later.

<a href="http://answers.polldaddy.com/poll/2950502/">Typo enclosure and iTunes metadata</a><span style="font-size:9px;"><a href="http://www.polldaddy.com">polls</a></span>

Published on 24/03/2010 at 21h44 by Frédéric de Villamil, tags , , ,

Typogarden is back from the grave

After a few months being slightly brocken, Typogarden, Typo’s theme catalogue is now back from the grave, better, and more up to date.

I incidentally broke Typogarden while upgrading the Typo that was hosting it, and forgot to backup things before doing it. I had to change a few things in the new default theme and in every theme picture to make things right. You can now submit new themes at neuro[at]7el.net, and I’ll add them as soon as possible.

Published on 14/03/2010 at 17h55 by Frédéric de Villamil, tags

Release of Typo 5.4.3 Willy Ronis

We’re happy to release Typo 5.4.3, the third version of the Willy Ronis branch. Typo 5.4.3 fixes some nasty bugs that went through Typo 5.4.2 despite running tests before releasing. If you’ve been using Typo 5.4.2, you really should upgrade. And if you’re running any prior version, you should upgrade too.

Here’s the changelog:

  • Fixing a critial bug that made the page editor crash at loading.
  • Now sorting articles by publication date instead of creation date in the admin.
  • In the admin, comment forms fields are now filled with the user info. Url and email fields have been switched too to fit front end comment forms.
  • Extending the editor a little bit, easier to use now.
  • Ticket 143: Publish at post setting does not work
  • Fixing a bug in RDOC that raised an error when installing.

You can install Typo using the gem way or download the sources

Published on 14/02/2010 at 19h17 by Frédéric de Villamil, tags , , ,

Release of Typo 5.4.2 Willy Ronis

3 weeks after releasing Typo 5.4.1, and only 1 month after releasing Typo 5.4, we’re happy to release Typo 5.4.2, an important bugfix release. Don’t expect many feature here, even though we thought about some of them, it’s really a bugfix, and nothing else.

Typo 5.4.2 is avaliable as a source package on Rubyforge, or as a gem from Gemcutter.


We’ve split the attachments between images and non images assets. Provided you’re using the simple editor, you can now use a fancy images carousel and insert your images in your text within a single click. This comes with a nice set of thumbnails.

Finally, the long awaited “forgot my password” link is here. It will send you a new password whenever you lose yours. Cool isn’t it?

We’ve also done some optimization in the way Typo sends assets and manages cache. CSS and Javascript are now sent into 1 file, making them faster to load. RSS generation has also been fastened up.


A bug screwing up the editor when switching from simple to visual, causing users to lose their content when switching. Fixing that is a good reason to release today in itself.

A bug preventing your registration email to go when creating your account, making you lose your password unless you change it manually before logging out.

Fixed a security issue making the user passwords to be logged in clear in the application logs.

Fixed a bug causing CKEditor to crash under MS Windows due to the lack of symlinks on windows.

That’s all folks. See you in a while for our next update!

Published on 23/01/2010 at 19h42 by Frédéric de Villamil, tags , ,

Release of Typo 5.4.1 Willy Ronis

Only 1 week after releasing Typo 5.4, we’re back with another Typo release. Since it was fixing a major security breach, we had to release Typo 5.4 was released a bit faster than we expected, and we left some unfixed bugs here and there. Typo 5.4.1 is a bugfix version and should be considered as the first stable of the 5.4 series.

Don’t expect any new feature here, it’s only about bug fixing and code refactoring. We also started to work on the first Typo user’s guide as part of our documentation effort. The 0.1 version is provided in Typo 5.4.1. We’ve also upgraded every theme at Typogarden to make them 5.4.1 compliant.

Now that we’ve made Typo 5.4 slightly more stable, we’re open for any request for enhancement. So don’t mind opening a ticket if you feel something is missing.

Published on 28/12/2009 at 01h53 by Frédéric de Villamil, tags ,

Release of Typo 5.4 Willy Ronis

After 9 months of hard work, we’re proud to announce the official release of Typo 5.4 Willy Ronis, the most advanced and user friendly blogging platform on Rails. Despite having a minor version number, Typo 5.4 is a major release, coming with a lot of new features and some bugfixes as Willy Ronis was a great photographer who died this year at the age of 99. Since Typo 5.4 fixes some major security issues, you should really think about upgrading.

Typo 5.4 is also a major release because we had many contributors from all over the world sending new features and fixes along this year. After contributing for a while, Matijs van Zuijlen (http://www.matijs.net/) finally joined the core team in late February and did a great job on this release. We would also like to thank, in alphabetical order: Diego Elio ‘Flameeyes’ Pettenò, Edward Middleton, Erik Ostrom, Hans de Graaff, Jakob Skov-Pedersen, Kurt Werle, Michael Reinsch, Mike Mondragon, Wei Jen Lu, Yuka Ouka, jzellman, and mpagalan.

Published on 19/12/2009 at 11h00 by Frédéric de Villamil, tags ,

Typo gets blue (dabadi dabada)

Next release will come with a brand new theme called True Blue. True Blue is a simplified port of the theme I'm using on my own blog. It's a nice, clean, 2 columns blue theme coming with Twitter native support.



Hélène's Typographic is a great theme, but we needed something more casual. To quote Matijs' own words, the default theme should be one that anyone could start off using, no matter what their blog was about (like the Kubrick theme half the Wordpress blogs use).

Since True Blue is using its own helpers, you may need to restart your Typo installation to have it work after enabling. We're working on fixing this.

Published on 18/10/2009 at 17h59 by Frédéric de Villamil, tags , , ,

News from a summerish Typo

This has been 4 months since Typo 5.3 release, and this calm month of July may be the perfect occasion to look at what happeded on the Typo planet.

Cyril and I have been quite busy lately. He quited his job and started a new adventure in a new company. Cyril also moved to Paris, which is great as we’re now able to gather and work together, when we have time. He’s also been dedicating more time to Oupsnow, a bug tracker he’s writing in Merb. I’ve also been quite busy lately, starting lots of Rails projects around Twitter, having less and less free time left by my daily job, and starting a number 3, delivery due next December, so I’ll have to move soon. And that takes a lot of time too.

Hopefully, we had many contributors who came to help us while we were too busy to care about Typo. Erik Ostrom updated Wordpress converter, Michael Reinsch fixed some bugs and did some nice refactoring, and Wei Jen Lu did a fantastic job on translating Typo to Chinese. Wel also had a couple of people submitting patches fixing bugs on Lighthouse. May they be all thanked for the great job they did.

Our main concern lately has been reducing Typo memory footprint. We’ve already dropped lots of useless code and fixed a few bugs, even though there’s still lots of work to be done. By useless code, we mean 3 things:

  1. Removing dead code that is no longer called anywhere. And there was plenty of it, trust me. Typo is an old house, inhabited by lots of different people, and every house needs a bit of cleaning sometimes.

  2. Code that’s trying to reinvent the wheel when the same functionnality has been integrated into Rails for a while now. I know we still carry a lot of this one, and we still have a lot of refactoring to do.

  3. Code that should simply not be in a blogging engine core and can be moved elsewhere as a plugin. Deciding what to keep and what to drop is not always easy, but that’s the usual step in the life of a software.

I’m not really sure yet, but I don’t think Typo next release will carry any major feature. Instead, we’re focusing on performance improvement, bug fixes and usability improvement here and there. I guess it’s a needed step to take before restarting on a fresh, clean ground.

Published on 12/07/2009 at 15h05 by Frédéric de Villamil, tags , , , ,

Powered by Publify | Photo Startup stock photos