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.

  • gamermanh@lemmy.dbzer0.comEnglish
    1·
    4 hours ago

    Ok i get it, it’s best practice to do rushed releases without QA because users are the free testers.

    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 definitely had no way to know that their own app was incompatible

    They knew, and told you, right on the app page

    Idiot user who believed their newsletter "update now, hub 9 is the best thing ever

    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 fucking 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.