v12.0.0 Upgrade Experience Rating 😡↘️↗️❤️

JohnB

On a scale of 1 - 10 what rating do you give your v12 upgrade experience (not the delay just how the upgrade went).

1 - is garbage and everything sucks, enhance is horrible I want a refund.

10 - is perfection couldn't have been better, I'm taking Adam out to dinner.

Comment the number below

wenani

JohnB Was this thread really necessary

Kosta

JohnB the upgrade is okay but seems like they didn’t test much… even when they was saying they testing it.
Bugs that come up seems like they didn’t bother they to upgrade and experience that bugs… lol

cPFence

JohnB

Without a proper beta channel, there will always be some issues, no matter how much testing is done—nothing beats seeing software run on live, production servers.

That said, Adam’s support and efforts over the last two days have been phenomenal. I totally understand that setting up a full beta program is neither cheap nor easy for a small team, but maybe involving a few selected volunteers from this community as beta testers could be a good middle ground. I’m sure plenty of us would be happy to help, and it would likely lead to smoother releases.

In any case, for big updates like this, it’s always a good idea to wait at least a week before upgrading—let others test the waters first!

boltflare

9/10

gmakhs

3/10 Enhance NEEDS a BETA branch way to many issues with UI etc that could have been prevented if there was a BETA release before stable

btraill

gmakhs Ah yes, another uplifting take from the official Minister of Doom & Gloom. Your dedication to finding the dark cloud behind every silver lining is truly unmatched.

gmakhs

btraill its not about finding the dark cloud, i am being realistic and pointing out issues, expecting the Enhnance team to act on those comments which they do, and things are improving.
Its a commercial Service, Stable version needs to be stable, Merchant need time to adjust their products (Cpfence etc), yes support acts fast and short issues out, but trust is built on reliability, stability and organization

JohnB

gmakhs Merchant need time to adjust their products (Cpfence etc),

Completely agree. I'd make a beta channel that can only be accessed via custom install script. No way to switch to beta from the interface. This will avoid "I switched to beta and everything sucks I need support" have a big banner that says "NOT FOR PRODUCTION USE" too.

Anyway LET'S GET MORE VOTING HERE. Someone should create a thread for DISCUSSION related to the experience.

JohnB

wenani You're tone implies you think this is another complaining thread.

I haven't upgraded yet so I have no stake in this. This wasn't intended as a "vent about the upgrade" thread or argue about people's opinions.

Merely ratings -- good and bad.

gmakhs

Kosta The team has become more transparent, the release was present as ready ! but it wasn't and many features didn't even make it to the release , and also the bugs we found the first minutes,
BUT

This seems to be a learning experience for the team and they seem willing to change and improve, also they did started being more honest - open, this is something i respect.

Things looking positive

JohnB

gmakhs also they did started being more honest - open, this is something i respect.

This but I found it very disappointing that immediately after they started, suddenly many posters got way more dramatic. I really thought the openess would calm people. I have said that many times. But what actually happened is people getting more worked up.

If people want openness and honesty about delays they HAVE to behave better than this.

Kosta

Adam get mad probably, we all was pushing him and he said fk this and let the v12 release come up not finished and tested lol

Adam hope you can see now how much we can help by testing things and reporting bugs. Please make beta releases so we keep pushing things.

DDread

Who need testers when have customers?

Kosta

DDread I need testers!
So when I got production cluster with 1k websites none of them to email/bother me that something doesn’t work or their website is down when I do perform upgrade. Otherwise I get bad reviews/services and I loose my investment completely.

gmakhs

JohnB its normal for people to be Dramatic, they Delayed a Release since August, with the excuse being the last few months oh we run tests to make sure is stable, they released it, and people realized that no actually good testing had occur (see laravel, database,UI issues). People updated thinking this is a STABLE update and it wasn't .... all that leads to anger.... and is understandable....

Personally i lost faith to Enhance being able to BETA test and until there is a BETA branch i won't be in a hurry updating to the next version before is few weeks old.

My PRODUCTION server are not there to test

Also there is a bug with the new release and LARAVEL website, which i have been experiencing on the the 11 version on backup restore and migrations, i reported it but was never solved so i am happy it might be solved now that so many people are facing it

ecknz

I at a rating of about 6/10 points taken for each issue.

Upgrade was easy but....

I upgraded and had issues with two servers connecting to mariadb repo so the upgrade only half worked and Adam fixed it up within around 30 -45min from time ticket was created last night NZ Time.

Might be due to this.
12.0.2 - 13th February 2025
Enhanced
During the database server conversion from Docker, dependency errors whilst removing potentially conflicting packages are now non-fatal.

Backups that are already stored on the server are not displaying on the server gui but are under the website once a backup is created. New backups are not displaying on the backup server gui.

Total number of snapshots
0

Backups taken in the last 24 hours
0

Sites are still working but have these issues to fix

DNS records are not displaying under any domains except for the control panel and if a server hostname is deleted and added again. I removed and added back anything that did not have custom records as I'm using Cloudflare.
Cloudflare settings have dropped off under integrations and can not add back in.

These might be due to using Ubuntu Pro for the 1st issue or they are all related to the db issue

JohnB

gmakhs People updated thinking this is a STABLE update and it wasn't .... all that leads to anger.... and is understandable....

Absolutely. I was referring to people losing their mind when Adam said the update was postponed for a few days.

But I absolutely agree their testing was not sufficient. Beta channel is needed.

cosmoshosting

Mixed thoughts

Adam was incredible fixing some self inflicted issues during the update, but in practice executing the scripts on the wrong machines or out of order should not have caused an issue and had safety's built into it.
Updated expecting some minor issues to beta test out for the community as an early adopter, but did not expect to encounter show stopping serious breaking issues. Thankfully bulk of my customers are on DA so it wasn't a big deal. Had this been a production environment like many others it would have been critical.
Little frustrating so many issues we are all running into, either shows testing was insufficient where it mattered or not reflective of real world installs which is a big problem. I guess we were asking for it running the update on 12.0.0.0 but someone had to go first. It's not like most of us were updating from v10, had custom changes, using an obscure OS or had a overly complex environment.
Reinforces the clear need to have a Beta test channel for select people and work with partners like cPFence and OpSheild who should have had early access so they could have day 0 releases ready.

This is a huge update, so hopefully it's all smoother sailing from here on, but it certainly should be a learning point for Enhance with some key takeaways for future updates. Once again, congrats to Enhance for the milestone.

wpflys

My other company focuses on software development, and we really aim to roll out bug-free software. We put in days of testing, yet somehow bugs still slip through when we go live. The tricky part is that the more customizable the software is for end users, the higher the chance of bugs cropping up. For instance, with Enhance, one client has a typical setup and experiences no issues, while another client installed something that the Enhance team didn't consider, which could potentially mess up the system. Plus, as we add more features, there's more ground to cover in testing, and sometimes we overlook things that should work fine, only to discover they’ve broken even though we didn’t change that code.

Adam and his team's quick response to fixes has been quite remarkable. I know from past experience that beta branches can really slow things down, especially with a smaller group of developers and testers. If I were in their shoes without a big team and budget, I wouldn't go for a public beta. However, I would set up a private beta for folks like cPFence—other software developers who can effectively test and provide feedback, while also making sure their software works well with the upcoming release.

I can't give it a proper rating just yet since I'm waiting to upgrade, but after hearing about everyone’s experiences and the way Adam and his team are handling things, I'd lean towards an 8.