And it failed spectacularly.
We only needed a simple form, but we wanted to be fancy, so we used “nextcloud forms”.
The docker image automatically updated the install to nextcloud 30, but the forms app requires nextcloud 29 or lower. No warning whatsoever. It’s an official app, couldn’t they wait that it was ready for NC 30 before launching it? The newsletter boasts “NC hub 9 is the best thing after sliced bread” yet i don’t see any difference both in visual or performance compared to NC hub 2
Conclusion: we made our business to rely on nextcloud forms as a signup form, but the only reason we were using it was disabled who knows how many weeks ago.
You literally used the wrong version. As I stated: the app you’re talking about clearly states it does not have a stable release for the version of nextcloud you’re running.
They knew, and told you, right on the app page
You said it, not me. I tried being nice but that really is what happened: you fell for what the marketing team wrote and skipped basic IT steps in doing so. Now, rather than just admit you made a mistake that a LOT of people have made (including me, I’m a removeding idiot too) you are whining and doing your best to me talk gymnastics this into you being a victim of something
How you managed to convince your IT department of anything with a knowledge that shallow and an attitude like that I’ll never know. Grow up.
When on my personal install the music app was broken after an update for months, I didn’t complain at all. Because I went to see who was the maintainer: owncloud. Not their fault. In this case was my fault. Definitely my fault and without sarcasm. A third party plugin is expected to have problems after updates. Completely understandable. They’re even competitors.
First party plugins instead, MUST work at all times versus the latest stable release. It’s the reason I didn’t check compatibility.
This is the concept I want to say. It’s not hard. I’m not saying “the update process must be idiot proof”. When removed like this happens, it completely erodes trust in users. It’s not stable, it’s beta. It’s a tiny detail. It’s just a number on the manifest. What does it cost to update that number to 30 for the forms app? (The “incompatible” version runs perfectly fine when the check is overridden)
But no, let’s defend this behavior of moving fast and breaking things for no reason, like that issue thread on GitHub where users are rightfully pissed that the Windows nextcloud desktop client reboots without confirmation and fanboys are dismissing it “eh the cloud indicators in explorer.exe are so important, must reboot at all times, what’s the problem”
Do you agree that first party stuff must work? (unless it’s discontinued)
Would you expect Microsoft Office 365 being disabled after upgrading to Microsoft Windows 11?
And finally, how I persuaded the it department. Here I make a list of all the members:
We were just searching a way to host a worthless survey that nobody is watching instead of paying $350 to Surveymonkey. We drank the marketing cool aid and assumed that something heavily promoted just 6 months ago would be supported. But this is unreasonable.
Solution 1: waste a week doing your suggested way of multiple installs and custom unit tests and every quarter check carefully everything because nextcloud “stable” is as stable as a house of cards.
Solution 2: delete nextcloud and write a form in PHP+HTML in an afternoon, don’t have the same problem with nextcloud 31 next quarter.