Absolutely, and as soon as we can confirm things we will. It's good! You'll be happy.
Yes, that can be updated with the latest version from your account.
I hope to be able to confirm some exciting news about the next steps for Perch, but unfortunately it's not quite there yet. As soon as we're able to tell you about it, we will.
I'd love to see examples of the site you've built with Perch or Runway that you're most proud of.
If you had to pick one, which would it be? And was it Perch or Runway? Which add-ons did you use?
Up next, I'm looking at putting some of the add-ons into GitHub. That's not always as straightforward as you think, as I need to check the licensing for any dependancies etc. But my intention is to begin with Blog.
I've just put out a 3.1.7 release fixing what I hope is the last of any PHP 7.4 compatibility issues that have been reported. I've also addressed an issue for MySQL 8.0.4 and up that was flagged.
I've been looking as to how I can accelerate the progress of Perch 4, and one of the main stumbling blocks is the promised user interface refresh. If I can scale that back then a lot more can be shipped a lot quicker.
Thanks for the detailed notes, all. They've helped me identify and fix nearly all the above issues.
The only ones I've not been able to address are the weird PhotoShop EXIF issue (need to source some images to reproduce) and the CSP issue, which I'm not sure is a simple fix.
We’ve updated Perch with some compatibility 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, and those wanting to receive technical support.
What does it fix?
This release fixes the below issues:
- Fixes a deprecation notice about magic quotes when running in a PHP 7.4 environment
What features and improvements does it add?
This release does not add any new features.
What impact does it have for my clients?
This update should have little or no impact for your clients unless they were experiencing any of the above issues.
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
- Perch will update itself when you log in.
Hi all. Thanks for your understanding with this. My first priority is getting Perch and Runway working correctly with PHP 7.4, and then moving our addons on top GitHub and making them available for PRs.
The reality of this process is that PRs need reviewing and testing, and that often takes just as long as writing the code. Therefore if it's going to be successful, I think we realistically need a few people who are going to be willing to participate in the reviewing.
I'm going to look at she what aspects of the work done on v4 can be ported back into v3 so that functionality can be used.
Due to things changing and me needing to split my time differently, I'm not sure what the roadmap is. There's a bunch of work done on v4, and I need to figure out whether I scale back on the initial 4.0 and ship it, try and roll those features into a 3.x and ship it, or wait until I've got more of 4.0 done.
There's been some talk of compat issues with PHP 7.4, so I'd want to track those down and see what can be patched.
The link seems to keep changing. Do they expire?
Thanks! Seems like nginx doesn't always reload like it should at the end of the SSL renewal process.
Have you checked all the options here? https://docs.grabaperch.com/perch/configuration/database/
If there's something you need to be able to set but can't, we're just using PDO so it should be easy to add.
Thanks for the thoughts above. The situation is that Perch and Runway under the current license model do not generate enough income to keep me working on them full time. Progress on v4 is slow because the time I can afford to dedicate to it is less than it has been in the past.
This is not that usual - it's been the situation before with Perch, where I started it as a side project alongside client work. It was a full time job for two of us for a while, then just me, and now it's back to being just one project of a few. Dynamic server-rendered CMS solutions aren't a massively growth market, and that's fine.
So progress is still being made, updates are still coming, and support is still here. Perch isn't about to stop or disappear or anything like that. It's just that at the current volume of license sales I need to do other work to make sure I can pay my mortgage and feed the cat.
Is the issue that you're concerned about hitting the integer size limit?
You can just hit /perch/addons/apps/perch_blog/update/ in your browser.
I'd expect list.html to get the perch:after but not the perch:before