It’s been a while since you haven’t heard of us, and we first wanted to wish you a happy new year. As 2013 is starting, we’re happy to release Typo 6.1.2, the second of the Remi Ochlik series, nammed after a French photographer who was killed in Syria a few days after getting a World Press Photo, the most prestigious award for photojournalists.

This new Typo release comes with a major security bugfix that affects every Ruby on Rails version so far, and make your hosting vulnerable. If you’ve been using a prior Typo version, then it’s time for you to upgrade as soon as possible. This is mission critical, no kidding.

Download Typo 6.1.2.

New feature and improvements

Typo 6.1.2 is the first one to run out of the box on a Heroku instance. You just need to change the config/storage.yml file to switch to Amazon S3. This will make Typo deployment much more easier, and we plan to make it even more simple in the next few months.

Typo’s been translated in a few more language, we’re happy to welcome the Norvegian and Simple Chinese versions. Other translations have been improved as well.

The possibility of Typo sidebar plugins have been extended with the possibility to add new settings on existing plugins without reloading them.

Bug fixes

This version also provides the usual bug fixes:

A bug in the article list within the admin has been fixed. Selecting “all articles” would not display drafts.

Some usability issues regarding the menu highlight have also been fixed.

Solves an issue where the SEO titles would not be saved when submitting the form.

Autosave when using the visual editor has also been saved.

Published on 18/01/2013 at 22h42 by Frédéric de Villamil, tags

Release of Typo 6.1 Remi Ochlik

After a few months of musing, working and slacking, and a few commits too, we’re proud to announce the release of Typo 6.1 “Rémi Ochlik”. Rémi Ochlik was a French photographer who was killed in Syria a few days after getting a World Press Photo, the most prestigious award for photojournalists.

Typo 6.1.0 is the first release designed for Ruby 1.9 only, and the last one for Rails 3.0 series. Oh, and it’s still not running on Heroku even though some people managed to do it with some limitations.

As usual, you can download Typo 6.1 as a zip or tarball file, and give it a try on our demo site.

What’s new?

This release was meant to be dedicated to bug fixing and improving our base code. It also comes with a few nice feature.

Bootstraped, a new default theme

True Blue 3 is not our default theme anymore. It was replaced by Bootstraped, a new Twitter Bootstrap 2 based theme. Bootstraped is meant to be an easy to use framework for theme developers to create new templates. The choice of Bootstrap was an easy one, as none of us is a designed.

Bootstraped theme

A redesigned back office

The administration was also revamped with Twitter Bootstrap. It’s still running Bootstrap 1.4, as 2.0 was released after we finished the work. Swithcing would have delayed this release too much.

The new editor

The new editor, easier to use with more visibility.

The comments listing

The comments listing. The color pills make knowing what’s what easier.

Other feature

Initial database loading: users don’t have to run rake db:migrate when starting Typo for the first time. Trying to connect to the blog loads the database schema and data.

CKEditor was upgraded to 3.6.2. It now supports modern browsers and is a bit more stable.

User can now create categories within the editor.

Fully customizable 404 pages.

URL shortener can now be used to external links, always better to promote your brand.

Added a per state filtering on articles and draft listing: default (everything but draft), published articles, drafts, publication pending, withdrawn

Added custom permalinks for categories.

Gone feature

If you don’t use them, drop them! We’ve removed a few feature from Typo. Some of them will come back later, some not.

So long Typogarden and thank you for the fish

Typogarden is no more. We’ve lost the domain, which ended its long and painful agony. All these themes were a hastle to maintain, most of them were designed back in 2005, and no one had the time to care about them. This also means no more theme catalogue, which was removed from the admin.

Typogarden will come back under another form, maybe as a featured theme catalogue with the most up to date Typo themes.

No more complicated categories interfaces

We’ve removed the Javascript based category reorder interface. Categories are now be ordered by name, which looks like the most likely way to do it. This is a first step to sub categories as the order interface prevented from having them.

Bye bye theme editor

A theme editor is a great ad handy thing when it’s complete and actually working. This one was working but not complete and practical enough to be left as is. We had the choice between fixing it and removing it. It will probably come back later, under another form.

Squashed bugs

We’ve fixed a bunch of bugs, some of them being reported by you, some of them discovered by use.

Closed issues

Issue #46: Fixed comments management bulk operations.

Issues #48, #55: ActionView::Template::Error (settings was supposed to be a Hash, but was a String).

Issue #57: Fixed CKEditor file upload.

Issue #62: Fixed redirects not being correctly updated when updating a permalink.


Fixed the way permalinks are generated.

Fixed switching back and fort between simple and visual editor.

Now using publishedat, not createdat to determine when comments shall be closed.

Fixed a bug with controllers having empty indexes rendering errors.

Fixed a bug setting up a post as published everytime you edit it even for a draft.

Fixed comment moderation when using Akismet.

Fixed comments filtering when not running Typo in English.

Fixed autosave buttons display.

Now causes bundler to fail when database.yml does not exist.

Avoids accidentally loading old drafts.

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

Long time no heard from us? Come on, we're still moving!

It’s been a while since we last posted here. Obviously, we all have been pretty busy since th last time we released a Typo version. Spring came, then winter, and as Europe seems to be freezing as hell, some of us started to move again, one commit after another. I’m not sure how it started, but there’s something wonderful with open source projects: take a dormant project, and have just one commiter starting to push code regularly, and you’ll see other maintainers leaving their hibernation state.

Typo 6.1.0 is not out yet, as there is still some work to do, mostly bugs to squash and documentation to write, but we believed it was a good time to make a sign, and maybe put ourselves under pressure to be sure we release something good.

If you have some spare time and want to help us, here’s what you can do: pull Typo master from our git repository, install it locally or on your server (sorry, we’re still not Heroku compliant but we’re working on it), play with it, and report every bug you find. And if you really have time to help, you can even fix some of them and send us a pull request.

Oh, and if you ever happen to come here, you’ll see Typo next default theme running.

Published on 08/02/2012 at 21h37 by Frédéric de Villamil, tags

Typo 6.0.9 for Rails 3.0.10 – security fixes

We’re releasing tonight Typo 6.0.9 as Rails 3.0.10 brought many critical security fixes that would affect Typo, which means you really should upgrade now. This version also brings a couple of improvement some bug squashing and Yannick’s usual refactoring and performances tweaking.

You can download Typo as a zip file or a tarball.

The security issues addressed by Rails 3.0.10 are:

  • Filter Skipping bugs
  • SQL Injection issues
  • Parse error in strip_tags
  • UTF-8 escaping vulnerability


It’s now possible to create a new category within the article editor. This quite useful feature brings Thomas back from the dead and this makes us very happy.

Squashed bugs:

Displaying a password protected article within a category would make Typo crash when using the default layouts.

Using Typo standard live search views in a theme would make the application crash.

Issue #42: creating a new user from the administration crashes the application.

Fixes an issue with Redcloth 4.2.7.

Issue #39: Time.parse apparently hiccups when the timestamp string contains “GMT+0000 (UTC)”

Fixes a bug where attachment thumbnails would not be created at upload from the editor and API.

Fixes a bug in the new sanitization module when running under Ruby 1.9.2.

Once again, we want to thank the growing Typo community for their help on improving their favourite blogging engine (at least we hope so), and, in particular Huy Dinh for fixing some too long existing bugs.

Published on 01/09/2011 at 16h53 by Frédéric de Villamil, tags

Release of Typo 6.0.8 - Bug Fixes

Being the eighth of the Irving Penn series, this new Typo release comes only 3 days after the latest one, but it fixes a bunch of serious bugs that were discovered while using Typo 6.0.7 in the wild.

As usual you can download Typo 6.0.8 at the usual place, and give it a try on our demo site.

Adding per tags and categories templates

Typo is now able to provide a different template according to the category and tag you visit. This is useful for some sites which need such a level of customization. To use them, just add a views/categories/category-permalink.html.erb or a views/categories/category-permalink.html.erb file in your theme. Typo will use that file when displaying this category.

Bug fixes

Fixes a bug in the meta title generation when displaying an article, a category or a tag.

Fixes the custom tracking field making the site crashing when used.

Fixes a bug on tags removal not working.

Moving our bug tracker to Github

We’ve decided to move our bug tracker from Lighthouse to Github. In the past years, Github ticketing system has gained in feature and maturity while Lighthouse has been stalling, not being really convenient to use. This move allows us to centralize our tools in a single place. The new bug reporting place is now https://github.com/fdv/typo/issues

It’s been the third release in 11 days, but thanks to all our beta testers, I hope it’s the latest bugfix one. We want to thank in alphabetical order Mitch Pirtle, Lars Tobias Skjong-Børsting, Mathieu Poussin and Rhaamo for their bug hunting operation.

Published on 13/08/2011 at 09h12 by Frédéric de Villamil, tags

Release of Typo 6.0.7 - Bug Fixes

After releasing Typo 6.0.6, we realized that we left a few critical bugs unfixed. It seems that none of us actually ran our tests against Ruby 1.9.2, and things that were working under certain circumstances were breaking against a different environment.

So this release provides nothing bug bug fixing, which is not so bad, after all.

File upload was completely broken due to a behavior change in ActionDispatch::Http::UploadedFile between Rails 3.0.2 and Rails 3.0.3. File upload in itself is pretty hard to test, and we failed at this point.

Image resize was completely broken too due to a version change of minimagick. Reverting back to minimagick 1.3.3 did the trick.

Under PostgreSQL, initial migration would set an empty post_type despite a default set to read. It seems that PostgreSQL won’t fill the field value when created with existing inserts.

Mathieu Poussin added Recaptcha support on all bundled themes.

Pages view was broken under Ruby 1.9.2 due to an encoding issue. There was also an encoding bug in post_type edition and creation.

Despite extensive testing, pagination was broken due to a buggy will_paginate 3.0.4 beta. Reverting to 3.0.2 did the job.

Last but not least, a change in the way Google handles RSS queries caused dashboard load to take ages.

That’s all (for now). We’ll try to to better this time.

Published on 10/08/2011 at 18h03 by Frédéric de Villamil, tags

Release of Typo 6.0.6 – a major one

5 weeks after releasing Typo 6.0.5, we’re proud to release Typo 6.0.6 into the wild. With 403 files changed, 8526 insertions and 4961 deletions (before generating the CHANGELOG) this is our biggest release of all time. This was made possible thanks to Yannick François joining the core team, the growing amount of active contributors and a very crappy weather above Europe during our summer holiday.

You can download Typo 6.0.6 at https://github.com/downloads/fdv/typo/typo-6.0.6.zip or https://github.com/downloads/fdv/typo/typo-6.0.6.tgz. A demo is set up at http://demo.typosphere.org.

Typo 6.0.6

What’s under the hood?

Rails 3.1 ready

We’ve got a long way since Typo was first released for Rails 0.6 and Ruby 1.8.4. Typo 6.0.6 is now Rails 3.1.0 ready and runs on both Ruby 1.8.7 and 1.9.2. We’re now waiting for Passenger (mod_rails) to be fully Rails 3.1 compliant to switch to this new exciting Rails version.

URL shortener

Adoption of microblogging has made URL shorteners an important part of our daily browsing life. Hosted services may disappear one day or another taking your shortened URL with them, so we have given Typo its own URL shortener.

When you publish a new article, Typo generates a shortened URL that will redirect to your content. No more risks of disappearing shortened URLs, YOU keep the control.

Recaptcha support

Silvio Relli did a great job adding Recaptcha support to Typo 6.0.6. Recaptcha is a captcha system that both fights against spam and uses successful decodings to helps digitise books.

You can use both Recaptcha and Akismet on a Typo installation.

New toys for plugin developpers

We wanted to make Typo easier to extend for plugin developpers. Typo 6.0.6 introduces a bunch of new tools for them.

Users custom fields

Users can now have an infinite nummer of custom fields, that will be used by plugins developpers without having to modify the database. Settings are easy to add and easy as pie to use.

Contents custom fields

Articles and pages can now have an infinite nummer of custom fields, that will be used by plugins developers without having to modify the database. These custom fields are easy to add and easy as pie to use.

Custom routes for plugins

User defined plugins can now use their own route without changing the original routing files. This allows plugin developers to create powerful extensions without to worry about what Typo’s routing file looks like.

A powerful SEO oriented blogging engine

We’ve worked a lot on SEO, aiming at being as powerful as Yoast SEO Plugin on Wordpress. This release is a first step with the following feature.

Support for rel=’canonical’ in pages header to avoid duplicate content.
A canonical page is the preferred version of a set of pages with highly similar content. It’s common for a site to have several pages listing the same set of products. For example, one page might display products sorted in alphabetical order, while other pages display the same products listed by price or by rating. For example: http://www.example.com/product.php?item=swedish-fish&trackingid=1234567&sort=alpha&sessionid=5678asfasdfasfd http://www.example.com/product.php?item=swedish-fish&trackingid=1234567&sort=price&sessionid=5678asfasdfasfd If Google knows that these pages have the same content, we may index only one version for our search results. Our algorithms select the page we think best answers the user’s query. Now, however, users can specify a canonical page to search engines by adding a link element with the attribute rel=”canonical” to the head section of the non-canonical version of the page. Adding this link and attribute lets site owners identify sets of identical content and suggest to Google: “Of all these pages with identical content, this page is the most useful. Please prioritize it in search results.”
A custom template for meta title and description

Since meta title and description are very important for SEO, it is very important to be able to setup its own content. Typo now provides powerful customizable templates for both of them, with nice default enabled.

Making meta keywords optionnal

Since search engines do not consider meta keywords anymore, some people want to disable them to save on their page weight. This option makes it possible.

New content templates

Typo can now handle multiple content types through dedicated templates. Let’s say you want to display text articles and pictures only. Just create the content type, write a quick template for rendering, write your article, and your done. This new feature comes with handy helpers to generate per template menu…

This makes Typo theming even more powerful.

Control your cache from the admin

The long removed cache sweeping interface is now back, with interesting statistics about cached files.

Attachment thumbnails

Attached images are now generated in 3 sizes: original, medium and thumb. Both medium and thumb sizes can be defined in the administration.

Pictures albums in lightbox

Typo Lightbox macro now supports set parametre, which allows you to create nice photo albums.

More readability and usability

The admin sections have been reorganized for more readability and usability. We’ve redisigned some interfaces, work still in progress.

Code refactoring

Typo code is as old as Rails, which means we still carry old, deprecated code. This version brings lots of refactoring, dead code removal, speed optimization and even more testing.

Norwegian translation

Lars Tobias Skjong-Børsting has been doing a great job providing a full norwegian translation in an impressively short time.

Bug squashing

With code refactoring usually comes bug squashing. This version got rid of more bugs than a full tank of DDT would have, without the cancer effect.

A community effort

Typo 6.0.6 would have never been possible without our community of contributors, listed in alphabetical order: Huy Dinh, Fish, Justin B. Kay, Maarten Mulders, Silvio Relli, Melanie Shebel, Lars Tobias Skjong-Børsting, Eric Sorenson, Yule.

Published on 02/08/2011 at 11h25 by Frédéric de Villamil, tags

Creating advanced Typo plugins

2 days ago, there was a guy called Fish who joined us while I was idling on #typo. He was asking for a gallery plugin for his Typo blog. As I’m a photographer, having such a plugin had been on my TODO list for like years now, so I told him I would do a quick proof of concept during my daily train commute. A few hours later, when I went back home, the plugin was working. It was very simple, displaying files uploaded on a Typo blog with thumbnail, pagination, medium size and large size displayed in a lightbox. Indeed, it wasn’t enough, and Fish came back asking for multiple albums and picture selection, caption, so I came back to work. As a developper, Fish could probably have done it himself, but I’m more familiar with Typo internals, and even I didn’t know how far I could go with Typo plugin integration.

Tonight, during my daily commute, I extended my gallery plugin with full admin and frontend integration. The gallery is not working yet, but the biggest part is working: integrating a complexe plugin in a Typo blog. I wanted to share this with you as a HOWTO.

Before trying this, please be sure you’re using Typo HEAD as Friday April the 8th, or a Typo version above 6.0.4 (even though it’s not released yet) as you’ll need the route.rb modification I had to do.

Creating the plugin

As Typo plugins are just plain Rails plugins, creation is kinda trivial.

<typo:code> ./script/rails generate plugin typosampleplugin </typo:code>

You’re now going to create some folders to reflect a Rails application tree:

<typo:code> cd vendor/plugins/typosampleplugin mkdir -p app/controllers/admin app/models app/helpers/admin config app/views/admin </typo:code>

Good, you’re now ready to code the main stuff. Edit your new plugin, and let’s go!

Making your code accessible

Now, you’re going to make Typo access your code. Edit your init.rb file and add the following:

<typo:code lang=’ruby’> PLUGINNAME = ‘typosampleplugin’ PLUGINPATH = “#{::Rails.root.tos}/vendor/plugins/#{PLUGINNAME}” PLUGINCONTROLLERPATH = “#{PLUGINPATH}/app/controllers” PLUGINVIEWSPATH = “#{PLUGINPATH}/app/views” PLUGINHELPERPATH = “#{PLUGINPATH}/app/helpers” PLUGINMODELSPATH = “#{PLUGINPATH}/app/models”

config.autoloadpaths += %W(#{TypoSamplePlugin::PLUGINCONTROLLER_PATH} \

                        #{TypoSamplePlugin::PLUGIN_HELPER_PATH}      \
                        #{TypoSamplePlugin::PLUGIN_VIEWS_PATH}       \

ActionView::Base.send(:include, TypoSamplePlugin::Helper) </typo:code>

The routing

Unless Rails generators, your plugin won’t be allowed to change routes.rb. We want our end users to remove them if they don’t want them anymore. So we’re going to create our own config/routes.rb. It’s going to look like this:

<typo:code lang=’ruby’> ActionController::Routing::Routes.draw do |map| map.connect ‘sampleplugin/:action’, :controller => ‘typosample’, :action => ‘index’

%w{ sample_plugin }.each do |i|

map.connect "/admin/#{i}", :controller => "admin/#{i}", :action => 'index'
map.connect "/admin/#{i}/:action/:id", :controller => "admin/#{i}", :action => nil, :id => nil

end end </typo:code>

I know, we’re still using Rails 2 routing DSL. It’s bad but Rails 3 can’t handle everything we do.

The first block is for your frontend controllers, the second one for the admin. Easy as pie isn’t it?

The models

She’s a model and she’s looking good. I’d like to take her home that’s understood.

Add your models files in app/models exactly like on any Rails application. You can use any Active Record relations you want and access or extend existing Typo models.

To create your database schema, edit your init.rb file, and add the following code:

<typo:code lang=’ruby’> unless ::TypoSamplePlugin.tableexists? ActiveRecord::Schema.createtable(TypoSamplePlugin.table_name) do |t|

t.column :name,  :string
t.column :description,  :text

end end </typo:code>

Couldn’t be easy heh? Now let’s switch to the front and back office thing.

The front thing


To be able to display your content within your Typo blog layout, every front end controller will need the following code:

<typo:code lang=’ruby’> class TypoSamplePluginController < ActionController::Base unloadable layout :themelayout beforefilter :template_root

def template_root

self.class.view_paths = ::ActionController::Base.view_paths.dup.unshift(TypoSamplePlugin::PLUGIN_VIEWS_PATH)


def theme_layout

File.join("#{::Rails.root.to_s}/themes/#{Blog.default.theme}/views", Blog.default.current_theme.layout(self.action_name))


end </typo:code>

There’s certainly a cleaner way to do it by not repeating the code, but I’ll dig it later.


Nothing special here. Really.

The backend thing

OK, now you want to give your plugin a fancy back office? Let’s go.

Adding your module to the admin

Edit your init.rb. In your model creation block, add the following:

<typo:code lang=’ruby’> admin = Profile.findbylabel(‘admin’) admin.modules << :typosampleplugin admin.save

publisher = Profile.findbylabel(‘publisher’) publisher.modules << :typosampleplugin publisher.save

This will update both admin and publisher profiles giving them the rights to access your plugin admin.

Now, let’s add them to the access control list (and the menu as well). This is still in init.rb

<typo:code lang=’ruby’> AccessControl.map :require => [ :admin, :publisher, :contributor ] do |map| map.project_module :typosampleplugin, nil do |project|

project.menu    "My plugin meny",  { :controller => "admin/typo_sample_plugin" }
project.submenu "My submenu", {:controller => "admin/typo_sample_plugin_other" }

end end </typo:code>

Edit your lib/typosampleplugin.rb and add the following:

<typo:code lang=’ruby’> module Helper def classtyposampleplugin return classselectedtab if controller.controllername =~ /typosampleplugin/ class_tab
end end </typo:code>

This will allow you to manage the tabs highligh in the admin.


Your controllers will go to app/controllers/admin and will all look like this, pretty like normal admin controller:

<typo:code lang=’ruby’> module Admin; end

class Admin::TypoSamplePluginController < Admin::BaseController layout ‘administration’ unloadable


end </typo:code>


Typo plugins admin views look like normal admin views. Minimum code is:

<typo:code lang=’ruby’> <% @pageheading = (‘Sample plugin’) %> <% subtabs_for(:typosampleplugin) %> </typo:code>

You can access any admin helper like saveorcancel or linktonew.

Here we are (born to be kings). I’ll release Typo Gallery when I finish it, which could happen very soon as I’m thinking about quiting Flickr to host my photos somewhere like I used to do with Wordpress + Gallery2 in the past, many, many cycles ago.

Published on 08/04/2011 at 17h08 by Frédéric de Villamil, tags , , , ,

Moving to a new server... and to Ruby 1.9.2

If you can read this… I love starting a blog post with that sentence, it always teases something great, exciting, or just new. So, if you can read this, then, we’ve successfully moved to our new ass kicking server: Quad Core Xeon, 16GB RAM, 2*2TB hard drive on a Gigabit port with as much trafic as the machine can handle.

But that’s not the point.

This blog is running on a yet experimental but apparently working Ruby 1.9.2 compliant version. If you’ve been running 6.0.4 lately, then you can also try running Typo on a Ruby 1.9.2 environment.

This does not work out of the box though. You will need an UTF-8 aware Ruby 1.9 compliant database driver, just like sam-mysql-ruby. To do so, just edit Typo Gemfile and replace the gem 'mysql' line by gem 'sam-mysql-ruby'. If you’re using a custom theme, you’ll probably have to fix your theme encoding too.

As I’ve said, this is very experimental. However, if you’re willing to test this, we’ll be glad to hear your feedback. Just one thing though: don’t complain because you’re using a database driver that’s not UTF-8 compliant: we can’t do anything about it.

Published on 06/03/2011 at 17h43 by Frédéric de Villamil, tags , ,

Release of Typo 6.0.4 : lots of bug fixes and cosmetic improvement

It’s been 3 weeks since we last released a Typo version, and we want to thank all our users who provided great feedback – mostly bug reports, nobody’s perfect. We’ve had a hard time fixing them as these bugs were mostly due to the upgrade to Rails 3.0, but tonight we’re happy to release Typo 6.0.4, fourth of both the Irving Penn series and 2011.

General Improvement

Integrated version checker

When displaying the dashboard, typo will check for the latest release and will display a message accordingly:

  • A notice if Typo’s just a minor version behind.
  • A warning if Typo’s a sub version behind.
  • An error message if Typo’s a major version behind

Our dashboard was almost completely redesigned, making information easier to get and prettier.

Utility Sidebar Widget

A utility sidebar widget was added, displaying various links to Login page, RSS, Typo documentation. This Widget is enabled by default when creating a new blog making the sidebar prettier.

Editable RSS description

RSS description is now editable from the admin. You can add as much HTML as you want to make nice RSS footers.

French Translation

Having 3 Typo commiters out of 4 being French while having an incomplete French translation full of mistakes was a shame. This is now fixed thanks to great work by Ollivier Robert and Sylvain Abelard.

Bug fixes

Invalid publishing time when using a non UTC timezone.
With Rails 2, Active Record used to store contents using local time for timestamps. Rails 3 uses UTC instead, creating a gap between the publishing time and the user’s time. Typo 6.0.4 fixes this making Active Record behave like it should on Rails 3.

Broken theme editor.
A change in the way File.read should be called between Ruby 1.8.6 and Ruby 1.8.7 broke theme file loading. Also theme editor did not raise an error when trying to load non existing files.

Broken migrations when creating a new blog.
Rails 3 upgrade broke initial migration as it was trying to use a non loaded model.

Broken sidebar save button
Upgrade to Rails 3 with use of prototypelegacyhelper plugin broke many AJAX saving feature. This caused sidebars not to be saved anymore.

Broken image links in administration style.
Background images would not load when using Typo in a sub URI.

Broken cache system.
The way caching used to work caused a stale file descriptor bug having the cache not being generated anymore after a sweep.

Broken cache system with sub URIs.
Cache could not be accessed when using a site deployed in a sub URI, making it useless.

Broken sites with https.
Blogs using https would break because Typo was only expecting URLs to start with http only.

Broken Flickr and Lightbox macro filters.
By escaping macro tags, BlueCloth was breaking Flickr and Lightbox macros. This would happen when using Markdown, Textile or Markdown + Smartypants.

Published on 23/02/2011 at 11h30 by Frédéric de Villamil, tags

Powered by Publify | Photo Startup stock photos