Perch Update 2.7.7
13 January 2015
We’ve updated Perch with some new features and bug fixes discovered through our support forums. This is an update to Perch and Perch Runway.
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:
- Fixes bug with the
resource_logdatabase table growing overly large
- Fixes bug with duplicate results in asset search results
- Fixes ‘Yes/No’ localisation bug for delete confirmations
- Fixes bug with category output in
skip-templatefor some filtering methods
- Prevents unnecessary backslash stripping when
magicquotesis not enabled
What features does it add?
- Adds a bulk upload dropzone to Assets app
- Adds image metadata (titles and tags) extraction to asset uploads
- Improves performance for saving items containing lots of assets
- Improves the look of asset listings with larger, squarer thumbnails
What impact does it have for my clients?
This update should have no impact for your clients unless they were experiencing any of the above issues. There are slight differences to how uploads are handled via the Assets app, which you may wish to take note of.
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 new
- If updating from <2.6, copy the
templates/categoriesfolder across, and add
- Perch Runway users updating from <2.7.4, copy the
perch/addons/apps/perch_dropboxfolder to get the latest updates
- Perch will update itself when you log in.
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. Perch Runway requires PHP 5.4. You should always run the newest release of PHP available to you.
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.