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.
I’m happy to announce that Publify 8.0.1 has been released. This is a small bug fix release, but it fixes some very annoying ones.
I’d like to thank you all, every contributor who helped with this release.
It’s been 5 months since Publify 7.1, and considering the figures, Publify 8.0 is the biggest release we ever pushed in 9 years: 474 commits, 71 issues closed, 8 contributors, 567 files changed, 60,767 additions and 45,166 deletions.
But you probably don’t care about numbers that much, except if you’re wondering whether or not the project is till alive. TL; DR: it is.
The project itself has known one big change, moving from Fred’s personal Github account to a dedicated organization. We have been thinking about it for a while, and we believe it’s the best we could do for Publify.
Last summer, we started to rethink what we wanted Publify to be. At a time where online publishing is more or less split between Wordpress, hosted platforms and static engines, being “only” a blogging platform had no meaning anymore. We started to extend publishing capabilities, choosing Twitter pushed short notes as a first step before we add more content type. This led to Publify 7.0, and once again we knew it was the way to go.
Before adding these feature, we wanted Publify 8.0 to rebuild the whole user experience. It had to be simpler, clearer and better, far from the MS Word 97 style that prevails in Web publishing since more than 10 years.
This meant a simpler interface with a single, smaller menu, getting out of the old create / read / update / delete scheme when possible, merging some sections and finally removing lots of things. This also means using the most of large screens capabilities, using responsive layouts as much as we could, even though it made the job more difficult at some point.
The editor, it has been completely revamped, following the way opened by both Medium and Ghost. We’ve pushed aside everything that may distract you from writing. The editor goes fullscreen, and you can even pick up a white or dark background at your convenience. The post settings are 1 click away from the editor so you won’t feel lost anyway. We know how much work is left to get a really classy tool, but we’re working on it.
The notes have got improvement. When replying to a tweet, Publify now displays the original tweet so readers can keep the context this was done.
Users profiles have been improved to. Each user now has its own detailed page with avatar, contact links, short bio and indeed the published content.
The old categories VS tags separation is no more. We merged the first into the seconds as a strict categorization has no real meaning on most blogs. Don’t worry about your URLs, we took care of everything, eventually creating the redirects you needed.
The excerpt has been removed. Excerpt was meant to display a different content on the listing page and on the post itself. It was an interesting feature, but only a handful of people, if none was using it, and it made the editor more complicated than necessary.
The old Typographic theme is not part of the core anymore. It has moved to its own project and will still be maintained.
The old XMLRPC backend has been discontinued. This means Publify does not support desktop clients anymore. This choice has been motivated by the fact that the APIs it was relying had not been updated for 10 years, and that most desktop editors are not maintained anymore either. Web browsers capabilities have evolved, and you can now have a fairly decent editor with local saving without the need of a desktop application.
Publify has been around for 9 years now. Rails was not 1.0 yet, and some of our code was older than you can ever imagine.
Publify 8.0 got rid of most of that legacy code. The old Prototype based helpers that made Rails famous back then left the building. Prototype itself has finally been replaced by Jquery, and Rails i18n allowed the Globalize based translation system to enjoy a deserved retirement. Most helpers have been removed too, as most of them were only used in one place.
This should not affect you unless you’re running custom themes and plugins. If so, have a look at the Bootstrap theme to see how we’re now working.
That’s all folks, you can now download Publify, or give it a try on our demo platform.
It’s been scratching us for a while now, and we finally did it: Typo is no more, long live Publify! There are many reasons why we changed your favorite blogware name, leaving behind us a 7 years old brand and not always glorious history.
Typo took its name from a Typo Tobias made into his agenda, giving him a few hours to start coding the blogware that once powered Rails official blog, but let’s be honest, it’s a stupid name for a blogging engine, a really stupid one.
Making typos is not something you would expect when writing quality content, and we indeed expect our users to produce quality content. Typos make content look dumb and their producer look careless if not illiterate.
On the other hand, even though Publify may not be the best, most original name, it means what it should mean: something meant to publish, which is not so bad after all.
Open your favorite search engine, and look for typo. My bet is you won’t find many things related to Typo. If you’re lucky, our main site will come on first page, but I’m not even sure it will happen.
Google brings 65,300,000 results for Typo, most of them being related to typography, Publify has only 3460 entries. I’m sure you see the point, but finding resources for Publify will become easier as time goes.
There was a CMS called Typo3 long before Typo appeared. Typo3 is an enterprise CMS developed in PHP, and many people would make the confusion. Typo3 has been around for more than 10 years, and we did not mean to overlap on that name. It actually caused more problems that it solved, because many people were asking us about Typo3.
typo:code macros won’t work anymore. They’ve been replaced by the same
publify:code macros. We’re providing a migration that makes your content work with
Your old themes should still be working. If not, just replace all occurrences of TypoPlugins by PublifyPlugins, and all occurrences of Typo by Publify.
Your homemade plugins probably won’t work, because the TypoPlugins class they inherit from doesn’t exist anymore. To fix them, replacing TypoPlugins by PublifyPlugins in your code should do the trick. Don’t forget to restart your Publify blog after doing the changes.
That said, we’re now going to go back to work to release the first Publify version during the summer. Have a nice, sunny blogging.
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).
Powered by Publify | Photo Startup stock photos