Publify Versions Save

This minor release updates Publify to use Rails 5.1

• Upgrade to Rails 5.1 (#814)
• Update Danish translations (#831)
• Extend Polish translations (#829)
• Fix a bunch of issues (#840)
• Remove outdated converters
• Fix google analytics tag rendering (#849)

This is a bug fix release. It provides the following updates:

• Enforce use of at least Rails 5.0.4.
• The email field is handled correctly when users sign up (#819)
• The sign-up and login forms use the correct layout (#819)
• Theme-related JavaScript files are served correctly (#823)
• Russian translations have been updated (#820)
• The link_to_author setting that no longer had an interface has been removed (#816)
• Dependencies were updated (#815)

This is a major release and brings big changes to Publify. First of all, Publify now uses Rails 5.0. Moving ahead to Rails 5.1 will come in Publify 9.1, but for now this smaller step should make it easier to migrate any customizations.

Second, Publify has been split up into several Rails engines (publify_core, publify_amazon_sidebar and publify_textfilter_code). This should allow easier re-use and customization. For now, the core engine still contains many parts that can be considerd optional. These may be extracted into their own gems at a later stage.

Apart from those two large changes, there are some smaller potentially breaking changes:

• Publify now uses Rails' default method of setting secret_key_base in production: Through an environment variable. This means you will have to update your production environment so this variable is actually set.
• Support for Ruby 2.1 is dropped.
• Automigration is dropped. You will need to run db:migrate yourself.
• Support for using feedburner is dropped.
• Trackbacks and pingbacks are no longer sent. Trackbacks are no longer accepted.
• Full-page caching is dropped in favor of default Rails' Russian-doll partial caching.

All the little details can be read in the change logs:

• The main Publify change log
• The Publify Core change log
• The Publify Textfilter Code change log
• The Publify Amazon Sidebar change log

As always, ensure you have your database backed up before upgrading!

Alvaro Folgado identified several security issues in Publify that are fixed in this release:

• Rails' protection from CSRF was not active for all actions. This was fixed.
• Devise' password recovery feature was configured to behave differently for existing and non-existing email addresses. This has been changed to use Devise' 'paranoid' mode.
• Publify was vulnerable to CVE-2016–3714, a vulnerability in ImageMagick, on servers that have affected versions of ImageMagick installed. It now checks the mime type of uploaded files based on their content before processing with ImageMagick.
• Publify used Rails' cookie session store, making it possible to effectively log back in by using an older value of the session cookie. Publify now stores the session data in the database.
• The blog name was not properly escaped in the views used for Devise.

Additionally, the following small bugs were fixed:

• There was an error on the sign-in due to the use of a deprecated method in Devise.
• Failed resource uploads were reported as succesful.

It is recommended you update to this release as soon as possible.

Another simple bug fix release. This fixes a couple of bugs that were reported since version 8.3.1 came out. Have a look at the change log for more details.

This is just a simple bug fix release. It fixes some old bugs, and some that were reported since version 8.3.0 came out. Have a look at the change log and milestone for more details.

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:

• Make Publify multiblog-ready: All models should now be directly or indirectly linked to a blog, opening the way for finally supporting multiple blogs in some form. What form? That is still up for debate, but you can join the discussion in the GitHub ticket.
• Replace custom Publify authentication system with Devise. This just gives use less code to maintain ourselves.
• Replace custom Publify authorization system with CanCanCan. As with Devise, it's better to use a well-maintained gem for this.
• Remove Profile model. This wasn't really doing anything in standard Publify, but beware if you've put any customization there.
• Remove long-deprecated view_root method for sidebars. Just some simple house-keeping, but if you haven't been paying to Publify's warnings for the past years, this is a breaking change.
• Provide registration mechanism for themes, allowing them to be stored anywhere. This opens the way for turning Publify into a Rails Engine, and for having themes as plug-ins.

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:

• Dependency on Rails has been updated to 4.2, including recent security fixes.
• Migrations have been rolled up to 113 according to our upgrade policy. You must now first upgrade to at least version 7 before upgrading to the latest version.
• The default bootstrap theme was replaced with bootstrap-2. You can find the old theme at https://github.com/publify/themes-bootstrap.
• A Plain theme was added that uses only Publify's default templates with a sprinkle of custom css.

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 obviously have some work on automated tests.

#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 Publify release migrates from Rails 3 to Rails 4.

This does not make justice to @mvz and @ook tremendous work, but that's all it does, and that's a lot!