Perch Update 2.6.2
25 August 2014
We’ve updated Perch with some bug fixes discovered through our support forums. 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 or those wanting to receive technical support.
What does it fix?
This release fixes the below issues, and is a direct replacement for the previous 2.6.1 update, which was bad:
- Fixes a bug where removing a newly added asset did not work until page refresh
- Fixes a bug where deleting a category set didn’t always delete its categories
- Fixes a bug with categories losing their order when edited
- Fixes a bug where paging reported to be present when only one page was returned
- Fixes bug with assets bucket list when no assets are logged
- Fixes setup warning about missing license key
- Fixes bug with toggle sidebar not working
- API: fixes a bug with
*catch-all event handlers not being called
What features does it add?
This release adds no new features, it’s just bug fixes.
What impact does it have for my clients?
Perch 2.5 made user interface changes, especially around the uploading of images and files. You may wish to walk your clients through the changes on a staging site before making them live if updating from a version prior to 2.5. This update (2.6.2) makes improvements and fixes bugs but doesn’t change the interface significantly.
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/corefolder with the newperch/corefolder. - If updating from <2.6, copy the
templates/categoriesfolder across, and addcategoriesto yourconfig/apps.phpfile. - Perch will update itself when you log in.
Important note
Perch now requires PHP 5.3 with JSON support. Please check your diagnostics report before updating to be sure that your hosting supports these requirements.
We always advocate updating your staging or development copy of the site and testing the changes first. We do not recommend updating a live site without checking everything’s going to work first.
If updating from a version prior to 2.5 and using the Blog, Events or Comments add-ons, you should update those also.