V.9 Documentation supports PHP 7.4 LTS > Therefore v.8, incl. Addons, Support and Forums should be supported

In the v.9 Documentation, Portland Labs clearly writes on: https://documentation.concretecms.org/9-x/developers/introduction/system-requirements, that PHP 7.4 LTS (Long Term Support) is supported. Many Providers around the world keep PHP 7.4.
There are a lot of v.8 sites out there, many site owners depend on v.8 with php 7.4 LTS, the CMS even offers updates to this environment, currently 8.5.17.

Therefore v.8 addons, support pages, forum entries etc. should be supported, - at least for another 2 years.
Once v.10 is out, one could consider phasing out v.8.

3 Likes

There’s nothing keeping you from running the code you bought from our marketplace years ago until the end of time. We have clients that are running ancient versions of Concrete too, and while we don’t recommend it, nothing is keeping them from doing that and we use LTS to do our best to keep it secure.

That said, I’m struggling to understand why you think we should continue to sell these extensions now. This stuff is end of life, we don’t want people buying it for new projects.

I also struggle to understand why you think a developer who sold you a theme for $30 more than 5 years ago should be on the hook for providing upgrades for free now to keep something working on a legacy system that everyone is saying is end of life.

Happily, they don’t have to… They haven’t really been for some time, but since you’re keeping old code working on old systems, there’s no need to worry about updates.

I understand your position porting concrete to a commercial plattform. Unfortunately it leaves a lot of devoted users behind and left alone with their older installations.

1 Like

I’m not sure “porting concrete to a commercial platform” is a fair representation of what we’ve done here. Concrete is still fully open source under the MIT license. If we wanted to “port concrete to a commercial platform” we’d strip all the advanced functionality out of concrete (permissions, workflow, multi-site, multi-lingual, etc), call that Concrete PRO or something and sell that for thousands a year to compete with Kentico and Sitecore. We haven’t done that.

What we did do was take down a 15 year old marketplace full of abandoned products that were getting no support and replace it with a completely rebuilt marketplace with a codebase we can maintain. We removed any product that was getting no support, and we did change to a model where extensions would have a recurring revenue model instead of a one off in the hopes that it would motivate developers to keep updating their extensions over time.

If you’ve been upgrading your Concrete site over the years, the extent of the impact here is you have to reconnect to the community, which incidentally is wildly easier now.

If you’ve not been upgrading your Concrete site, again there is really no impact to you as you can leave that code up running on a PHP LTS setup for as long as you want. There weren’t updates happening to these v8 extensions happening anyway.

In addition to all of that, we’ve repeatedly made the offer that if someone has purchased a v8 or earlier extension and they need a copy of that package, we’ll do our best to go manually get it if they simply ask. That’s not a very scalable solution but at the end of the day, but we’re not trying to cause pain for anyone. If there’s something simple we can do to help, we’re always going to try.

What I do find a little frustrating at this point is being the whipping post for technology changing at all. Look Andy and I reminisce about how simple the web used to be vs. what we do today frequently. “Remember when version control used to be renaming index.html to index.bak and LeechFTP was all the CI/CD we needed? Remember when writing PHP didn’t feel like writing Java?” That’s a nice release to talk about after a beer on a Friday afternoon, but I can’t stop time.

I wish PHP 8 didn’t require the changes it did to code.
I wish the web projects I designed and built back in the aughts would have served those client’s needs forever.

That said, we work in a medium that changes a lot, and we need to move forward. We’ve put a lot of work into making upgrading workable. It’s pretty disappointing to be told we’re leaving “devoted users behind” because we don’t want to sell unsupported extensions and encourage use of end of life software.

2 Likes

Thanks for the smile about what “version control” used to be - brought back some good memories :slight_smile:

You certainly did a great job with Concrete at Portland Labs. Thank you.