Team Folder forms don't store results

[markruys]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Create a form
2. Move it to a Team Folder
3. Fill in form and click on submit

Expected behaviour

Answers should be added to the form results.

Actual behaviour

Answers are not stored.

Server configuration

FormVox: 1.2.0

Web server: Unknown

Database: MySQL 10.6.25

PHP version: 8.3.30

Nextcloud version: Nextcloud Hub 26 Winter (33.0.2)

List of activated apps

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

Browser

Browser name: Chrome/Safari

Browser version:

Operating system: Mac

Browser log

No errors in the browser log.

[Sam428-png]

Hi @markruys — thanks for the report. We can't reproduce this on our test setup (NC 33.0.2, MariaDB, default local storage, Team Folder). Form created, moved to Team Folder, submit goes through and the response shows up in Results. So there's something specific to your environment.

Could you share:

1. How did you move the form? Via the Files web UI (drag/drop or cut-paste), or via WebDAV/CLI?
2. Primary storage backend: local disk or object storage (S3 / Swift / MinIO)? Check occ config:list system | grep objectstore.
3. Server log during the submit — anything from OCA\FormVox in data/nextcloud.log (or System log in admin UI) right after you click submit?
4. What does the form file look like after a submit? If you have CLI access, cat path/to/yourform.fvform | python3 -m json.tool | tail -50 — is the responses array populated, empty, or missing entirely?
5. Are you the same user who filled in the form? Or did you fill it in with a different account (or anonymously via the share link)?

[Sam428-png]

Heads up @markruys — v1.2.2 is out with several related fixes (authenticated submit path now uses the admin-bypass loader, sections no longer pollute the results view, etc.). We couldn't reproduce your specific case earlier, but it's worth retesting on the new version. If it still happens, the diagnostic info from our earlier question would help: storage backend, server log around the failed submit, and a peek at the .fvform file after one submit attempt.

[markruys]

Apologies for the slow follow up. The issues still seems to be present.

Nextcloud Hub 26 Winter (33.0.3)
FormVox 1.2.2
Primary storage backend: local disk
Error log is empty

To reproduce:

Open FormVox
Create new form ("New Poll")
Choose as destination ("Opslaglocatie") a Team folder
Click on Create
Click on Share ("Delen")
Click on Create response link ("Reactielink maken")
Click on Copy

Open another browser, anonymously
Paste the link in the URL
Select an option
Click on Submit ("Verzenden")

Thank you!

Your response has been submitted successfully.

Close "Share form"
Click on Results

0 reactions

Open Nextcloud in the browser
Open Team folder
Download new-poll3.fvform

Contents:

{
    "version": "1.0",
    "id": "447fde2b-f6e7-46ba-bf71-5962aa6ee7e8",
    "title": "New Poll3",
    "description": "",
    "created_at": "2026-05-25T19:46:17+00:00",
    "modified_at": "2026-05-25T19:47:22+00:00",
    "settings": {
        "anonymous": true,
        "allow_multiple": false,
        "require_login": false
    },
    "questions": [
        {
            "id": "q1",
            "type": "choice",
            "question": "Wat is je voorkeursoptie?",
            "required": true,
            "options": [
                {
                    "id": "opt1",
                    "label": "Optie A",
                    "value": "a"
                },
                {
                    "id": "opt2",
                    "label": "Optie B",
                    "value": "b"
                },
                {
                    "id": "opt3",
                    "label": "Optie C",
                    "value": "c"
                }
            ]
        }
    ],
    "pages": null,
    "_index": {
        "_checksum": "",
        "response_count": 0,
        "last_response_at": null,
        "fingerprints": [],
        "user_ids": [],
        "by_date": [],
        "answer_counts": []
    },
    "responses": [],
    "downloaded_at": "2026-05-25T19:51:01+00:00"
}

[Sam428-png]

Heads-up @markruys — v1.2.3 includes a fix that's directly relevant to what you reported: appendResponseWithLock() now verifies the result of the storage write and throws if it silently fails, so you'd see a real error instead of a 'Thank you!' followed by an empty results page.

Also worth knowing: when you download the .fvform file via the Files UI, responses are stripped client-side for privacy. So your downloaded new-poll3.fvform showing responses: [] doesn't actually prove the write failed — it could be that the response is in the on-disk file but the results view isn't picking it up (a separate issue).

Could you upgrade to v1.2.3 (will appear in the Nextcloud App Store later today after automated review) and retest? Specifically:

1. Submit a response on the Team Folder form.
2. Look in the browser for an error. If you now see a real error after submit, the write is failing for a concrete reason — please share the error text and the server log entry (OCA\\FormVox lines) around that time.
3. If submit still says 'Thank you!' but results stays at 0, that's a different bug (results-view not reading what was written) and we'll trace it from there.

Either outcome moves us forward. Thanks for the very detailed report and config dump!

[Rikdekker]

Hi! Thanks for the report.

You're on FormVox 1.2.0. Since then, v1.2.3 (2026-05-30) shipped a fix that's very likely the same issue you're hitting:

Form submitted "successfully" but the response disappeared — Some storage backends silently rejected the response write while the UI still showed "Thank you!". The write result is now verified and a real error surfaces instead of a false success. (#97)

Team Folders use the same underlying storage as Group Folders, which was one of the backends that could silently drop the write.

Could you upgrade to 1.2.3 and re-test? If the submit still silently disappears, it should now throw a visible error instead — please paste that error here and we'll dig further. If submits work, this can be closed.

[markruys]

I've upgraded to 1.2.3. Indeed now I get an error message:

Storage write returned false or short write for fileId 2754 (wrote false of 2270 bytes)