CWP 1.8 is out, and has options for PHP 8.4 & 8.5

CWP 1.8 is out, and has options for PHP 8.4 & 8.5

I have not tried building 8.4 or 8.5 thru the CWP GUI, but it looks like it's on my to do list today.

# CWP 1.8: Finally PHP 8.4 and 8.5… but where is CWP really going?

Let's be honest: **seeing PHP 8.4 and PHP 8.5 finally becoming available in CWP 1.8 is good news.**

But is this really a major step forward in 2026?

PHP 8.4 was released in **November 2024**.
PHP 8.5 was released in **November 2025**.

We are now in **August 2026**.

That means CWP is roughly **21 months behind PHP 8.4 and 9 months behind PHP 8.5**.

This is not an unfair criticism. It is simply a fact.

And that fact should make the CWP community ask some serious questions.

---

## The problem is no longer just PHP

For a long time, a certain amount of delay could be considered acceptable.

But today, the gap seems to affect much more of the CWP ecosystem.

Administrators are waiting for answers regarding:

* new PHP versions;
* modern operating systems;
* modern web technologies;
* newer Apache and Nginx versions;
* HTTP/2 and HTTP/3;
* modern security technologies;
* virtualization technologies;
* performance improvements;
* backup solutions;
* integration with modern security products;
* and, most importantly, CWP's overall strategy.

The problem is that **we don't really know where CWP is going.**

And that may be the biggest problem of all.

---

# Where is the roadmap?

This is the question many administrators are asking.

**What is CWP's official roadmap for the next 12, 24 or 36 months?**

Which technologies are priorities?

Which operating systems will be supported?

When can we expect major releases?

Which features are actually being developed?

What has been abandoned?

What is simply delayed?

Today, getting clear answers to these questions is far too difficult.

And for administrators running production infrastructure, **uncertainty is a problem.**

We cannot build professional hosting infrastructure based on the hope that a feature will eventually arrive.

---

# The changelog needs to change

A changelog is one of the most important communication tools a development team has.

Yet CWP's changelog too often fails to provide a clear picture of the actual evolution of the product.

An administrator should be able to open the changelog and immediately understand:

**"This is what was developed. This is what is coming. This is what is planned. This is what has been fixed."**

That is not an unreasonable request.

It is basic communication for software that is used in production environments.

---

# Competition is moving forward

While CWP continues at its current pace, **other control panels are continuing to evolve.**

Modern technologies are released rapidly.

PHP versions move forward.

Linux distributions evolve.

Security requirements become increasingly demanding.

Hosting providers have to keep up.

And when a control panel falls too far behind, administrators naturally start looking elsewhere.

Not necessarily because competitors are better at everything.

Sometimes simply because they provide a stronger impression of **active development and a clear direction.**

---

# CWP still has something extremely valuable

And this is exactly why this discussion matters.

**CWP has a community.**

There are thousands of administrators who know the platform extremely well, have been using it for years, and would actually prefer to continue using it.

But that community needs to know that CWP has **a vision for the future.**

We are not asking for every feature to be released tomorrow.

We are asking for something much simpler:

### Give us a direction.

Tell us what is coming.

Tell us what is being developed.

Tell us what is delayed.

Tell us what is not planned.

And most importantly, **communicate regularly.**

---

# PHP 8.4 and 8.5 should be a beginning, not a destination

To be clear:

**Congratulations on CWP 1.8 and the addition of PHP 8.4 / 8.5.**

This is a positive step.

But it should not be considered the end of the problem.

It should be **the beginning of a new development cycle for CWP.**

A cycle with:

* more regular releases;
* a properly maintained changelog;
* a public roadmap;
* better communication;
* faster adoption of current technologies;
* a clear strategy for modern operating systems;
* and a long-term vision.

---

# The real question

So the question is not:

**"Does CWP 1.8 finally support PHP 8.4 and 8.5?"**

The real question is:

## "Will CWP remain technologically relevant over the next 3, 5 or 10 years?"

Because a hosting control panel cannot simply catch up with technologies months after they are released.

It needs to be able to **anticipate them.**

CWP still has a place in the hosting industry.

CWP still has a community.

CWP still has many loyal users.

But that loyalty should never be taken for granted.

**We want to continue using CWP.**

But for that to happen, we need to see that CWP genuinely wants to keep moving forward.

### PHP 8.4 and 8.5 are welcome.

**Now show us what comes next.**

## And there is another much more critical issue: backup and restore

It is impossible to seriously discuss a control panel designed for professional hosting without discussing **backup and restore**.

And on this subject, the situation is particularly concerning.

CWP's backup and restore system has been experiencing issues for months, and these problems have been reported repeatedly by users.

The problem is not simply that a bug exists.

**Bugs happen.**

What is concerning is when an issue affects such a critical feature as backup and restore, is reported repeatedly, and yet it appears that the underlying problem is never truly reviewed and reworked in depth.

A backup that works is important.

But a backup where **the restore process does not work reliably is not a real backup solution.**

When an administrator discovers that an account, database or files cannot be properly restored after months of reported issues, that becomes extremely concerning.

Backup and restore is not a secondary feature.

It is a **fundamental security and business continuity function** for any hosting environment.

At this point, what may be needed is not simply another series of small bug fixes.

The backup and restore architecture may need to be **properly reviewed and reworked**, with genuine restoration testing and a serious review of the issues repeatedly reported by the community.

Because ultimately, a hosting provider cannot afford to discover when disaster actually happens:

> **"The backup exists, but the restore doesn't work as expected."**

This is exactly where trust in a control panel is won or lost.

And this is why the community is asking for more than just a list of new features.

**We need the fundamental features to be reliable before continuously adding new ones.**

PHP 8.4 and 8.5 are important.

New technologies are important.

But **reliable backups, reliable restoration and overall system stability are even more important.**

Installed PHP 8.5 on PHP FPM without issue 

When try to install 8.5 on PHP Version Switcher it says Missing dependecies found: zlib (which is installed so maybe something pointing incorrectly?)

+1

@cgauthey

Sounds like you would be happier with another control panel then...

Show me 1 that does every one on your 2 posts.

But CWP does do things mentioned on your list.
You still have to be a sys admin to know how to work the admin panel and CLI to enable them.

@cgauthey

Sounds like you would be happier with another control panel then...

Show me 1 that does every one on your 2 posts.

But CWP does do things mentioned on your list.
You still have to be a sys admin to know how to work the admin panel and CLI to enable them.

@Starburst

You're still arguing about the wrong thing.

Nobody said CWP's servers stopped responding or that the version number can never change. A project can keep shipping the occasional update and still be effectively dead in terms of development, direction and communication.

And “show me one panel that does everything” is just a strawman. Nobody asked for perfection. The question is whether CWP is keeping pace with the ecosystem and communicating where it's going.

You keep pointing at version numbers as proof of life.

A version number changing isn't development transparency.

What changed?
What was fixed?
What CVEs were addressed?
What components were updated?
What's planned next?
What's deprecated?
What's supported?
What's broken?

Where is the roadmap?

If the answer is “you need to be a sysadmin and use the CLI,” that's not an answer either. Being able to hack around limitations doesn't magically turn an unsupported or undocumented feature into a mature product.

And “other panels have CVEs” is another distraction. Of course they do. The question is how quickly they respond, how they communicate it, and whether users can verify what was fixed.

As for:

Sounds like you would be happier with another control panel then...

That's probably the most telling response of all.

When legitimate criticism gets answered with “leave if you don't like it” instead of facts, documentation and a roadmap, you're not actually defending the product. You're defending your attachment to it.

CWP may still run.
CWP may still have useful features.
CWP may still receive the occasional update.

But that's not the same thing as being an actively evolving, professionally communicated project.

A heartbeat isn't the same thing as being healthy.

And after years of the same complaints stale/missing changelogs, unclear roadmap, slow adoption of current technologies, DIY workarounds and users repeatedly asking the same questions calling it “not dead” because a build number changed is becoming a rather low bar.

If you think that's unfair, don't tell people to use another panel.

Show us what CWP has actually delivered, where it's going, and what the official team is committing to.

That's the discussion.

I think it's fair for someone to suggest another panel given the list of needs and wants above.

It has never been in the DNA of CWP to provide that level of documentation and service and if that is hugely important to you there is only 1 panel you're ever going to get that from. CWP comes with some gold & some challenges, it has always required some admin skills to keep it honest but is also super easy on the bank balance.

I think it's fair for someone to suggest another panel given the list of needs and wants above.

It has never been in the DNA of CWP to provide that level of documentation and service and if that is hugely important to you there is only 1 panel you're ever going to get that from. CWP comes with some gold & some challenges, it has always required some admin skills to keep it honest but is also super easy on the bank balance.

@6Sense

That's pretty much where I ended up as well.

I moved to Webuzo Business Edition in February this year, and in roughly four months I've migrated my entire fleet over to it.

I also went with dedicated DNS servers in geographically separate locations. Yes, the additional DNS setup/licensing costs extra, but honestly, it was worth every penny.

And I have to say, I'm genuinely impressed with Webuzo.

The thing that surprised me most wasn't just the feature list. It's the overall experience of running it. The updates, documentation, current software stack, and the way everything fits together have made my day-to-day administration considerably easier.

And the support has been a huge part of that. Every time I've contacted support, I got a response. That's a pretty basic expectation when you're paying for a product, but after my previous experience, I really appreciate it.

CWP gave me a lot for the money, and I won't deny that. But after running production infrastructure on it for years, I eventually got tired of constantly having to fill gaps myself, work around things, or wait for the panel to catch up.

With Webuzo, I've spent the last four months doing the opposite: migrating everything and actually getting on with running the infrastructure.

I'm not saying Webuzo is perfect or that everyone should switch. But for my requirements, this has been a massive improvement.

The extra licensing cost including the separate DNS licenses is insignificant compared with the amount of admin time and headache I've saved.

Four months, entire fleet migrated, dedicated geographically distributed DNS, responsive support and I genuinely don't regret the decision.

This thing is amazing.