Perch Update 2.2.10

19 July 2013

We’ve updated Perch with a few bug fixes for issues discovered in 2.2.9. This is an update to Perch 2. Please read the full Perch 2.0 update notes if updating from Perch 1.

Do I need to install this?

This update is recommended for all users, especially those experiencing the below issues, or those wanting to receive technical support.

What does it fix?

This release fixes the below issues:

Note: the above fix for a bug with automatic output-stage HTML encoding could result in some of your templates displaying HTML tags as text after updating. Don’t panic. This happens when a field that contains HTML doesn’t have the right tag attributes to indicate that it contains HTML and therefore shouldn’t be encoded. The bug might have resulted in this looking ok, even if the tag was technically incorrect.

Find the corresponding template tag and add encode="false" to turn off output-stage HTML encoding for that field.

What features does it add?

This release adds no new features.

What impact does it have for my clients?

This update should not have any impact on users unless they are experiencing the above issues.

A note about database connections

Forthcoming changes in PHP mean that from version 2.1, Perch now uses a different method of connecting to the database. As part of that, we’ve taken the decision to explicitly select a UTF8 character set for the database connection. If your site currently doesn’t use a UTF8 connection, and you use non-ASCII characters in your content, you can set Perch to use your old character set in the perch/config/config.php file. e.g.

define('PERCH_DB_CHARSET', 'latin1');

Where do I get the update?

Log into your account and re-download the files. The download has been replaced with the newest version.

Always make a back-up of your files and database before updating.

Unzip the download and replace your perch/core folder with the new perch/core folder. Perch will update itself when you log in.

Previous updates