Publify

Making blogging easy

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

  • by Frédéric de Villamil 17/08/2011 at 06h39

    Hi James,

    I just saw your messages on IRC. Just FYI all developers are living in Wester Europe and you came at 6:02 AM for us, which explains why you didn’t get an answer. Please, come back anytime when we’re up and we’ll be happy to help you and answer your questions :-)


  • by James 17/08/2011 at 04h38

    Figures… I shoot from the hip and vent my frustration… I neglect to check my email because I am too busy trying to solve the issue on my own… and Jason at RedCloth sent me a new gem.

    He has fixed the gem… he responded within a few hours of my email to him. I would assume he will release the new gem soon.

    My apologies to Typo, RedCloth and Jason at RedCloth…

    Now I am taking my cranky @$$ to bed… I’ll bring up typo tomorrow… ;-)


  • by james 17/08/2011 at 04h17

    I’ve been on the IRC channel several times today… waited around for quite some time…. asked a number of questions… received no responses… I tried a number of different steps to attempt to install this app… At this point I’m not impressed with RedCloth… I do not view the issue as a GCC issue as someone suggested in a ruby forum somewhere… I do see an issue with not updating the gem when the code in the git repository has actually removed the -Werror option… which I did attempt to build but ran into other issues… like asking for an older version of rvm and not recognizing the newer one that was installed after I edited it’s Gemfile.

    At this point I would assume that if the gem is not going to be updated an FAQ for fixing the issue would show up… 5 seconds for a web guy to place it on the FAQ page… if RedCloth can’t figure that out then perhaps a post on the typo blog/dev page/anywhere with a workaround since you obviously DID get it to work would be helpful…

    So for your own information… as I am done… frustrated to the point of using static html5/css or perhaps just throwing a different app on my server.

    With RedCloth 4.2.7 installed as a gem:

    bundle install Fetching source index for http://rubygems.org/ Using rake (0.9.2) Installing RedCloth (4.2.7) with native extensions /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/siteruby/1.9.1/rubygems/installer.rb:551:in `rescue in block in buildextensions’: ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)

        /usr/local/rvm/rubies/ruby-1.9.2-p290/bin/ruby extconf.rb 
    

    checking for main() in -lc… yes creating Makefile

    make gcc -I. -I/usr/local/rvm/rubies/ruby-1.9.2-p290/include/ruby-1.9.1/i686-linux -I/usr/local/rvm/rubies/ruby-1.9.2-p290/include/ruby-1.9.1/ruby/backward -I/usr/local/rvm/rubies/ruby-1.9.2-p290/include/ruby-1.9.1 -I. -DFILEOFFSETBITS=64 -fPIC -O3 -ggdb -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings -Wno-missing-field-initializers -Wno-long-long -fPIC -O0 -Wall -Werror -o redclothattributes.o -c redclothattributes.c ragel/redclothattributes.c.rl: In function ‘redclothattributeparser’: ragel/redcloth_attributes.c.rl:26:11: error: variable ‘act’ set but not used [-Werror=unused-but-set-variable] cc1: all warnings being treated as errors

    make: *** [redcloth_attributes.o] Error 1

    With RedCloth 4.2.3 installed as a gem and after I edited the typo Gemfile:

    rake db:migrate –trace rake aborted! couldn’t parse YAML at line 183 column 9 /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in parse' /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:inparsestream’ /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:119:in parse' /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:106:inload’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/redcloth/formatters/latex.rb:6:in <module:LATEX>' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/redcloth/formatters/latex.rb:3:in’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/redcloth.rb:21:in require' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/redcloth.rb:21:in’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/casesensitiverequire/RedCloth.rb:6:in require' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/RedCloth-4.2.3/lib/case_sensitive_require/RedCloth.rb:6:in’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:in require' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:68:inblock (2 levels) in require’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:in each' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:66:inblock in require’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:in each' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler/runtime.rb:55:inrequire’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/bundler-1.0.18/lib/bundler.rb:120:in require' /var/www/typo/config/application.rb:6:in’ /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/siteruby/1.9.1/rubygems/customrequire.rb:36:in require' /usr/local/rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:inrequire’ /var/www/typo/Rakefile:4:in <top (required)>' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/rake_module.rb:25:inload’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/rakemodule.rb:25:in load_rakefile' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:495:inrawloadrakefile’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:78:in block in load_rakefile' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:129:instandardexceptionhandling’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:77:in load_rakefile' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:61:inblock in run’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:129:in standard_exception_handling' /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/application.rb:59:inrun’ /usr/local/rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/bin/rake:32:in <top (required)>' /usr/local/rvm/gems/ruby-1.9.2-p290/bin/rake:19:inload’

    /usr/local/rvm/gems/ruby-1.9.2-p290/bin/rake:19:in `’

    …dillinger…. out…


  • by Matijs van Zuijlen 09/08/2011 at 14h12

    Hi James, please do join us on the IRC channel. We will need to know what you tried, and what error messages you got. Without such details, it’s hard to help.


  • by james 09/08/2011 at 14h06

    I am pulling out my hair… I couldn’t use the version of Ruby that was included with 11.10 (testing) so now I am using rvm. I installed ruby 1.9.2p290 which still will not allow me to install typo. I’m not experiencing the “easy”. I’m running into frustration over and over. To be honest it is less likely to be a typo issue and more my own ruby ignorance. I’ve been trying to cut my teeth with ruby for going on months now and keep meeting problems. Very frustrated… I’ll likely jump on the irc channel in the next couple of days and see what I might accomplish there. The app looks nice and functional… I’d like to use it… I’m merely frustrated…


comment Release of Typo 6.0.6 – a major one

Trackbacks are disabled

Powered by Publify – Thème Frédéric de Villamil | Photo Glenn