I'm going to assume, that should someone purchase a standard Perch license (via the roundabout method) you'll get a license and it will be usable.
Usable, up to version 3.2 I would assume, which is exactly what is said when purchasing a new Perch license.
I don't really understand why there would be a notice in my account to say that Perch 3 licenses are not available if that's not true.
I would say, that the notice is referring to older version downloads only.
I get the following, once I click "Pay with Card":
It's quite clear that Perch is being discontinued in favour of Runway. At some point in the future I guess there will be an announcement for this.
How so, when we can still purchase Perch licenses?
The product is future-proof in terms of the CMS itself, so while for Cart, it seems that it is more a Runway product, I don't see how Perch could be considered discontinued, in particular when Runway and Perch are built on the same codebase.
This is what I get now in my account:
I can purchase any one of these licenses but Perch, is only for version 3.2
I was able to add a Perch license in my shopping cart, so there doesn't seem to be an issue, with respect to purchasing new Perch Licenses.
How long is a piece of string
SSL Certificates, changelogs and blogs; I agree should always be up-to-date and current.
Perch V4 availability.
Which developments do you mean? There have been no posts by Perch team on the forum recently.
Also, if I click the “Buy a license” button in my account, it tells me to buy a `Perch 4.0 single website license` @ € 65 as well as a `Perch Runway 4.0 single website license` @ € 219.
How am I going to explain to my 29 Standard Perch clients, that they will have to pay € 284, plus my work to transfer their site to Runway, for their next update? Some of them are tiny companies.
I might as well convince them to switch CMSes. Might be the easier sell, as things stand with the new owners’ communications and all.
(Sorry, am getting exceedingly bitter over this whole mess.)
I was able to bring up the cart, for Perch V4.
I am glad the ssl issue has been fixed. I think the difference in opinion on how perch should be developed comes down to use case. If you are using perch professionally to sell websites to clients then these sorts of issues are show stoppers that will hurt your reputation / business. If you are using it for personal sites then you don't really care about reputation and all these issues become easily worked around.
Some people, wish to develop e-commerce, others a professional website; some still, a personal website.
In relation to the last two points, there is no problem of which I am aware, however regarding the first point, I accept there are issues there but again, no indication they will not be fixed at any point in time.
Recent developments would indicate otherwise.
The last response from Perch on this thread was three months ago. So I'm going to remain concerned for now.
How long will this thread be needed?
How I look at things, is thus: prior to acquisition by venture capitalists aka the "new owners", drew did whatever he could to get the CMS, i.e., Perch up to scratch in terms of PHP8 compatibility.
The new owners, went on to fix any remaining bugs in this regard.
Does that not in and of itself allay any or all fears?
I think you can just delete your account @Perch.
Hi Simon,
I would like to be able to give more information, but as I can't log in locally, I would only be able to post diagnostics from the server, or live site.
Regards
I am getting this problem now, on localhost for some reason.
Deleted the php sessions, folder no luck.
Does anyone know of a remedy?
I would dispute, any assertion that 'the team' or 'owners' do not care, no matter how things *seem*.
It's not like Perch is broken, beyond repair now is it.
I’m concerned
I am not, and recent certificate issue resolution should alleviate any or all.
