Posts by justanotherdave

    We all know this isn't going to happen. At this point it's pretty obvious that they've taken more on than they can handle. They're either unable or unwilling to invest the time and money needed to create a viable product, and in the meantime what little users they had left are jumping ship, and I don't blame them.


    It's a shame as I'm sure this isn't what Drew and Rachel wanted Perch to become when they sold it.

    Did you go ahead with this? Which apps aren't PHP8 compatible at the moment?, do you know? We do have until November 2022 until PHP 7.4 becomes unsupported. I've recently developed a Perch site which uses Shop, Blog, Members, Forms and all seems well on PHP 7.4 running Perch 3.1.7.


    I'm hoping I can keep things running smoothly on 7.4 until either Perch is updated or I move all my sites over to Craft CMS. At least I've got a year to decide.

    justanotherdave have a look at HTTPS://expressionengine.com


    craft was born out of expression engine when it was a commercial CMS it’s now gone open source with a flourishing and good quality plug in community. I have tried both but EE is a better fit for my needs and I found the tag logic easier to understand . Also has a Fully featured e-commerce plugin as well as a cheaper alternative.

    Thanks, it looks good I might have to give it go. Would the commerce solution you mentioned be the CartThrob Add-on?


    I've always been a bit apprehensive of using open source when it comes to a CMS, as with no money changing hands they tend to get forgotten about when the developers lose interest and move onto something else. That's one of the reasons I went with Perch, which is kind of ironic given the circumstances.

    I really hope Perch does continue and things turn around.


    A viable alternative might be Craft CMS - https://craftcms.com. It's looks kind of what Perch could have been if development hadn't of stalled a few years back. It has an e-commerce option too. It's expensive though. You're looking at $1,200 per site with e-commerce included and then $259 / yr after that. It's not too bad at $299 per project and $59 / yr without e-commerce though. I might give it a go. I kind of hate e-commerce anyway so I could just up my prices for that as it's not something I really want to compete on price for. I guess it just goes to show that Perch's pricing system really wasn't sustainable in the long-term.


    Anyone else know of any other CMS that is like Perch and also well supported? I've used Wordpress before and don't like it so I don't want to go that route.

    I often use Perch in this way. The vast majority of the site is static, with the client updating something like a restaurant menu on one page or maybe a blog. It's what I like most about the platform and the main reason why I use it. Compared to creating a Wordpress theme it's a doddle and takes a fraction of the time.

    That sounds like uncommon user error.


    SKU's are widely understood as needing to be unique, it's the whole point. Entering "GRE" for both green and grey sounds like someone needs to type "what is an SKU" into Google! :-) We need less distractions towards V4, not more!

    Yep. It's user error. But in an area where a client is expected to enter data, just saying it needs to be unique isn't really good enough. If it's a shop with a lot of products or options they're likely not going to know if it's unique or not, especially for options.


    It would be better for the system to pick this up and inform you that the SKU you've entered isn't unique, rather than just allowing it with no feedback and then just not working. Any other CMS I've used other than Perch will either tell you it's not unique or put a number on the end to make it unique. So most clients that have used other e-commerce solutions before aren't going to be worried about if what they've entered is unique or not.


    I realise there's more pressing issues for V4 and shop. But your response reads like this isn't worth the hassle and should just be ignored? When it IS an issue that needs fixing.

    Gareth S I'm just adding products to a Perch Shop install today. And one thing which would be an improvement is that the system needs to check for duplicate SKUs. The SKU for options and products etc need to be unique, but it the system doesn't actually check if they are and allows you to have duplicate SKUs, which don't work.


    For example I created a colour option for my products, entered Green and Grey as options and used the first three letters as the SKU. So both were "GRE". I was able to enter these and save the options but then if I selected both green and grey as colours it would only create variants for the first entry which was green and completely ignore the grey option. As this is something a client would often do themselves I think it needs to check for duplicate SKUs and not allow you to create two which are the same.


    Could you pass this on to the dev team?


    Thanks :)

    So Perch Shop works on PHP8 then?? For some reason I thought it didn't.


    It would be great to have a download page somewhere for all the addons with versions. I know we have: https://addons.perchcms.com but unless I'm being dumb and have completely missed it, there's no way to easily check if any of these have been updated and that your site has the most current versions installed.

    I'm hoping for something like £99/site with a years worth of updates and support then £49/year after that. I don't think they're going to confirm anything here though. It'll be a more official announcement.

    I suspect the development has been outsourced overseas to be honest. The "development team" will be another company in India. Now I'm not saying there's anything wrong with that, it works for some people on a limited budget. But it can easily lead to issues with communication and they do tend to say yes to everything and give unrealistic timescales.


    At this point I'd just be happy with Perch 3.3 with addons on PHP8. Take your time with V4 and do it correctly. I think a mistake here will lead the remaining Perch users to jump ship and it will be a very hard to replace them.

    This is probably due to PHP version. Older versions of Perch show this error on PHP versions above 7.1 I believe.

    Thanks Gareth S


    Does that mean that all of the addons for Version 4 are also ready to go? And is Version 3 along with all the main addons now PHP 8 compatible?

    This. I have multiple sites using various versions of v3 and add-ons including blog, forms and shop. All need to be running on PHP8 by the end of the year as my host is discontinuing PHP7 support. I know there have been some recent updates to Perch core. But do the add-ons now also work with PHP8? There's been no mention that these have been updated too.


    If V4 is going to come with a new subscription based payment model it would be great to have an update to V3 which includes PHP8 support, just so I don't have to move all my clients over to a new monthly or yearly subscription at once!

    Just to confirm, Gareth S . Are addons also being tested and updated to work with PHP8?


    I usually use the forms add-on on most of my sites, and often blog too. Shop would need to be updated to support PHP8 as well. Ideally all the first party addons. Otherwise the work on core is a little pointless. I would say the vast majority of perch sites would use at least one of the addons as well.


    I assume all the addons support PHP 7.4 currently? As 7.3 is being deprecated on the 6th December and removed from my hosts supported PHP versions. Is there a version or update history page somewhere for the addons? So that I can check my sites have the latest addon versions when updating to Perch v3.2 or 3.3 when ready.

    I've recently built my first shop using Perch and it's gone very smoothly. I'm pretty clueless when it comes to PHP I'm more of a front-end developer, but I've got there with no issues and I'm happy with the result, as is my client. I'll echo the comment above, I really like that I can just build the front-end of my shop exactly how I want. I've used Woocommerce in the past and that is an absolute nightmare to work with.


    The docs for shop are OK, but they could do with some improvement. I think a video series like the current Blog add-on has with example files to follow along with would be a real help to new users.

    Hi hus_hmd , I'd just like to thank you for the instructions above :thumbup:. They worked perfectly for my search results page.


    Gareth S I do think that it's strange the image isn't included by default. It's a very common use-case to include a thumbnail image when returning a search on a blog. Perhaps something to add for the next update to the Blog Add-on? :)