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.

  • Moonrise2473@feddit.itOPEnglish
    115·
    3 months ago

    Manual docker upgrade issued my me after reading the official blog and newsletter. The upgrade notes described the new version as the best thing ever and didn’t mention that one of their selling points would be disabled without any notice.

    I’m starting to see a pattern in those comments like “why did you wear a skirt that night? It looks like you asked for it…”

    • non_burglar@lemmy.worldEnglish
      14·
      3 months ago

      Whoah, dude.

      Not only are you being told what could have and will ward off unplanned breakage, but you have somehow characterised yourself as an unsuspecting victim here? Inaccurate and really inappropriate comparison.

      You knew enough to take on deploying a service, now comes the grown-up part where you hedge against broken updates.

      • Moonrise2473@feddit.itOPEnglish
        18·
        3 months ago

        I don’t know if maybe it’s my bad english in explaining it or it’s your comprehension skills that lack something.

        I write it again for the 10th time: I’m 100% ok having 1-2 weeks of downtime, and this is why i do it live. It simply doesn’t make sense to dedicate several hours every month on testing if all i need is getting 3 useless surveys filled per year. If it was essential for work and i needed 99.99999% uptime i would directly subscribe typeform or surveymonkey. If tomorrow my install completely bricks and disappears in thin air, i would have lost 30 minutes of time and no valuable data. I literally spent more time designing the logo for the instance than managing it. This is just to state how unimportant the data stored on it.

        This post wasn’t made about “oh no i lost millions and all my irreplaceable data thanks to nextcloud stupid updates” but how stupid is to release something that breaks features that they’re using as selling point.

        ok, now that we established that my IT skills are lacking and i should be fired because one single survey couldn’t be filled, this is the release notes: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_30.html

        Please tell me where they say that this feature is automatically disabled and also tell me why you think that this is acceptable.

        I don’t understand why you think that is acceptable.

        I even can’t find other examples where a release is so rushed, that selling points are disabled without ETA. I never saw for Libreoffice 24 dropping support for opendocument files for a couple months just because they had to meet a self imposed deadline

          • Moonrise2473@feddit.itOPEnglish
            15·
            3 months ago

            go to watch who is the maintainer of nextcloud forms, then see if they could have known that NC 30 was about to go out or not

            It’s definitely not unreasonable that if I make product X and I make product Y, and they’re not compatible, then a bit of warning is suggested.

            Again, wordpress updates break plugins all the time, but automattic plugins (same people of wordpress) never break. Coincidence? They just launch a new wordpress without checking if woocommerce or jetpack don’t work?

              • Moonrise2473@feddit.itOPEnglish
                14·
                3 months ago

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

                They definitely had no way to know that their own app was incompatible, this is definitely a problem of the stupid user. Idiot user who believed their newsletter “update now, hub 9 is the best thing ever”. The user should have known that stable = untested beta

                Also, this issue happened exclusively to me in the whole world, because everyone else isn’t an idiot like me and checks 30+ release notes scattered in 30 different repositories to guess any incompatibility. I was lazy and only checked the main notes! Such an idiot! Why I didn’t check every single installed app? It’s just 30! Nextcloud devs couldn’t have known that nextcloud devs didn’t update the manifest of the forms app! I should have checked before! Completely my fault!

                Now if you excuse me I got an update to the Windows nextcloud desktop app and it must reboot after update because reasons even if there’s a GitHub issue with 200 angry comments about that. No wait! Stupid me! First I have to fire a VM and use a whole week to write automated tests that account for every possible combination of settings, language, power management, installed apps and so on. Otherwise I could lose a worthless survey that nobody reads and that will definitely get me fired!

                  • Moonrise2473@feddit.itOPEnglish
                    12·
                    3 months ago

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