Perch Update 2.1.1
29 January 2013
We’ve updated Perch with a number of new features and bug fixes discovered through our support system. 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 those experiencing the below issues and those wanting to receive technical support.
What does it fix?
This release fixes the below issue:
- Fixes bugs with using the
contains
,in
, andeqbetween
filter match types - Fixes a bug with content region ordering when using
perch_content_custom
- Fixes a problem with
hide-defalt-doc
andhide-extensions
conflicting on search
What features does it add?
This is purely a bug-fix release to address problems found in Perch 2.1. It 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 Perch 2.1 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.