I think there is another aspect worth adding to this discussion, because my experience with CWP support over the last few months has made me even more concerned about the current situation.
After the changes that affected the UI on a significant number of servers, I expected at least a proper technical explanation from CWP. When an update affects core administrative functions on production systems, users need to know what actually happened, what was changed, what is still affected, and whether there are any recommended workarounds.
Instead, after opening support tickets and asking very specific questions, the answers have essentially been: please be patient, everything will be fixed in the next update.
But that does not actually answer the questions.
I have also contacted the development/support team by email at least three times regarding technical issues. These were not complaints or emotional messages; they were specific technical questions that, in my opinion, should have been relatively straightforward for the development team to address. I never received a meaningful response.
This is becoming more concerning than the individual bugs themselves.
Bugs can happen. Regressions can happen, especially when introducing a major UI or architectural change. What matters is how a company handles them afterwards.
If a production control panel breaks part of its administrative interface, I would expect at least:
* a clear explanation of what caused the problem;
* proper technical documentation;
* a list of known affected components;
* a clear indication of what has actually been fixed;
* information about remaining known issues;
* and, most importantly, some indication of whether a given release is considered safe for production.
Instead, users are increasingly being asked to simply wait for the next update without being given enough information to make an informed decision.
For me, this is directly connected to the question I raised in my original post:
**Can I safely update my production servers?**
At the moment, the answer is still unclear.
And this is particularly frustrating because I have been using CWP for many years. I did not choose CWP because I wanted a managed service. I chose it because it gave me a practical way to manage my own servers while retaining control over the underlying system.
I would genuinely prefer to see CWP recover from this situation rather than migrate to another panel. After so many years, migrating multiple production servers is not something I would do simply because of a few bugs.
But there is a point where the lack of communication becomes a technical risk in itself.
If I cannot get a clear answer about what an update changes, what has been tested, which issues are known, and whether the release is safe for production, then eventually I have to consider whether continuing to run CWP is the responsible choice.
So I would actually like to ask the CWP team something very simple:
**What is the current official position regarding CWP 1.x stability?**
Is CWP 1.7 considered production-ready for existing installations?
If so, which of the major UI regressions reported by users have actually been fixed, and where is the technical documentation describing those fixes?
And if it is not yet considered fully stable, why isn't this being communicated clearly to administrators before they update production servers?
I think these are reasonable questions, and answering them openly would probably do much more to restore confidence in CWP than simply telling users to wait for the next update.
I still hope CWP gets back to the level of stability and reliability that made many of us choose it in the first place. But at this point, we need more than promises about the next update. We need information.
And I want to be clear about one final point: **if this transparency, communication, and technical documentation do not improve, then migration will eventually become a concrete necessity rather than simply an option.**
I would genuinely prefer not to go down that road after using CWP for so many years. But running production servers requires a reasonable level of confidence in the platform and in the ability to understand and manage changes safely.
If that confidence cannot be restored through clear answers and concrete technical information, then we will have to seriously consider migrating our servers to another solution.
Topic: CWP 1.7 – What has actually been fixed? Community feedback (Read 270 times)
