This release brings a lot of small changes and a few big ones under the hood. The big ones shouldn’t really change anything from a functional standpoint right now, but they will allow some new possibilities and directions in the future. Enough with the vague words, here is a list of large or breaking changes:
As always, there are many small changes as well. See the change log for details.
Publify master has been running on Rails 4.2 for some time, so a new release is long overdue.
Some important changes:
In addition, there have been numerous smaller changes, bug fixes and improvements. See the change log for details.
Short after pushing 8.1.0, we’re releasing a quick bugfix one. We’re obviously too serious about “release early, release often”.
#497 Publishing breaks before adding tags and publishing time.
#498 Pages and articles editor appears on 2 lines only
#499 Autosave is broken on PostgreSQL
This version does one thing: it migrates Publify from Rails 3.2 to 4.1.
It does not seem a lot, but there was actually a tremendous work from Matijs and Thomas to make it possible.
You may not be aware of it, but Publify is as old as open source Rails itself, and not only did they make our old code work under the latest version of our favorite framework, but they also modernized huge parts of our code.
It’s now time for them to take some rest, and for us to pick up the feature we want to see in the next version. Stay tuned!
We’re thrilled to announce the release of Publify 8.0.2. This is the last release before we migrate to Rails 4, and mostly a bug fix one. It fixes a denial of service security breach, so we highly recommend updating.
As usual, we want to thank our contributors. For this release, they are Alexander Markov, Benoit C. Sirois, Hans de Graaff, Soon Van, Tor Helland and Nicolas Bianco.
Très Acton has discovered a risk of denial of service by memory exhaustion in the way Publify comments user input are parsed.
#428 The editor save bar jumps up and down when typing with inconsistent behavior.
#429: The help messages can’t be hidden.
#431: Avatars in the dashboard last comments block are not inline with the comment.
#432: Dashboard inbound links widget is broken.
#433: The admin / content search does not bring anything back.
#443: When creating a post, tags are shown in white on white.
#444: The articles date picker does not allow to change the time the article is published.
#445: Using the articles date picker results in a 500 error.
#447: Marking content as spam using the thumb icon results in a 500 error.
#454: Media library: the JS refactoring removed the lightbox.
#456: Admin / sidebar: the help box should be in a blue block.
#475: Lots of unused assets to clear.
#482: Cancel links are not displayed correctly.
#488: File upload is broken.
Link caching issue (All cached links are the same basically).
Use a relative image path for blogs installed outside of the site root.
Archive page is not cached.
Improved Russian, Norwegian and French translations.
Upgraded to Rails 3.2.18.
Added support for a human.txt.
It’s been only 2 weeks since we released Typo 6.1.3 and Typo 6.1.4 is already here. 2 weeks ago, we were sure that Typo was stable enough to ensure a long term release while we would work on our new major release.
3 things prevented us to do so.
First, a new Rails version was released with another important security fix. Typo 6.1.4 comes with that fix so you should definitely upgrade.
Second, we had the opportunity to fix some bugs, and that was another very good reason to release.
Three, we have done a huge documentation effort lately, and we thought it would be a good idea to have it released as well. The doc is now used to automatically deploy our Web Site on typosphere.org. Oh, and we’ve also changed our Twitter account, you can now follow us on @gettypo.
Once again, we’d like to thank our contributors Marcel M. Cary, Nicolas Blanco and randomecho for their… contribution to Typo.
Moved #defaulttextfilter so Trackback can use it (Marcel M. Cary).
Fixed typo news and latest posts date format with distanceoftimeinwords (Marcel M. Cary)
Fixed Heroku deployment Gemfile (Nicolas Blanco)
Fixes a bug where already published articles publication date would be changed by autosave (issue 141).
Fixed secret token generation on existing blog (issue 142).
Fixed an issue where textfilter showed always as ‘none’, even if set before to markdown (issue 69).
I love how History tricks you by repeating itself. There’s a lot of irony in the way insignificant events build the perfect running gag in real life. 9 years ago, Tobias Luetke started Typo in a Starbucks because of a typo in his calendar. Today, I was in a Starbucks releasing Typo 6.1.3 because of a glitch in my agenda. History repeating.
I love free software communities too, when it stops arguing about politics and trolling licences to focus on code and releasing software for the fun of it.
Open source world is wonderful. The more active a project, the more contributors it find. Exactly 2 years ago, I was writing (in French) about how Github would kill open source software communities. I still believe a single word of it, even though Github is amazing to make project activity more visible. Typo has 1180 forks and is followed by 858 people without advertising about it. Latest release happened 2 weeks ago, and we had more contribution that I would have expected from 4 great contributors : Nicolas Bianco, Soon Van, Mcary, and Diego Elio Pettenò, who’s been packaging Typo on Gentoo for years.
Typo 6.1.3 is probably the latest of the 6.1 series, and a bug fixing only release. We’re now going to work on Typo 6.2, a feature based release.
For a comprehensive list of fixes, please refer to Typo 6.1.3 Changelog.
The biggest contribution was pushed by Nicolas Bianco. It fixes file upload on Amazon S3. His work andgreat ideas make Typo easier to use on Heroku than ever.
Soon Van has been doing a great work on i18n, documentation and interface consistency.
Diego Elio Pettenò fixed various plugins and text filters that make use of Flickr API.
Mcary fixed live search plugin and behavior consistency within the admin interface.
Ticket nº86 : Media list did not reload after uploading a resource.
Ticket nº103 : Fixes a security issue by changing the scret token at setup time. Displays a warning message when default secret token is used.
Ticket nº123 : fixes the links available on the dashboard for both contributors and publishers.
Ticket nº124 : Fixes the html editor look and feel when the window gets too small.
Ticket nº129 : the default theme would not take all the blog options into account.
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.
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.
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.
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.
This release was meant to be dedicated to bug fixing and improving our base code. It also comes with a few nice feature.
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.
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, easier to use with more visibility.
The comments listing. The color pills make knowing what’s what easier.
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.
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.
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.
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.
We’ve fixed a bunch of bugs, some of them being reported by you, some of them discovered by use.
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.
Powered by Publify | Photo Startup stock photos