Answering options cannot be added in v1.1.0

[nextcloud]

Answering options cannot be added in v1.1.0

[agentlibre]

It seems that this app was a one-shot project: https://help.nextcloud.com/t/were-making-a-forms-app/50271

I'm trying to raise awareness on the main NextCloud forum: https://help.nextcloud.com/t/awareness-on-a-sadly-dying-app-nextcloud-forms/70823

Perhaps you guys could help by mainting my post alive (comment, like, etc.)!

[forteller]

Same issue.

Does anyone have an ETA on a new version? Thanks a lot!

[githubDante]

Please issue an updated version with all commits included and everyone will be happy.

[Fry-4TF1V]

Is it possible to push last commits to the app store ? As a user of an hosted and managed Nextcloud I cannot have access to files configuration.

[schniepp]

Same problem here. NC17, apache, chrome, server:ubuntu-18.04, client:ubuntu-18.04.

I have to add that this is the first time for me to use the app, so I cannot say whether this is a regression in 1.1.0 or an older problem.

[joseams86]

I have the same problem too. I tried installing from the store, downloading from the web and it doesn't work, I also tried to install the previous version of forms but it isn't compatible with nextcloud 17.0.2

I hope someone knows the solution or update the error soon.

[fdrgit]

Same problem. Nextcloud 17.0.2 server on Debian 9 (stretch), forms 1.1.0 installed from the store. Tested with Chrome Version 79.0.3945.117 running on win10.
Was working fine with previous release of forms...

[born2webdesign]

Same here.
Is there anyone who doesn’t see this with NC 17(.0.2) and forms 1.1.0?
I suspect the problem is located in Forms and/or NC; but, FWIW: server is PHP 7.3, MySQL, Apache; client is Firefox 68.4.1 on Debian 10 (other clients, too).

[pwepwe973]

Sam Problem for me.
On NC 17 and Form 1.1.0

[mikweb2017]

Sam Problem for me NC 18 and forms 1.1.0

[githubDante]

Same here. Nextcloud 17 and the latest version of the app installed through the admin panel.

Console output:
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).
The console output indicates that $csp->allowInlineScript(true); needs to be set in PageController.php. (caused by a plugin). Also the latest commit to Create.vue f95b22c looks directly related to the issue. Tried some modifications but I've failed miserably.
I hope that it will be fixed soon as the app is currently in an useless state for me.

Edit:
The commit mentioned above actually fixes the issue discussed here. Finally, I successfully built the master branch. The commit however is not included in version 1.1.0 which is available in the Nextcloud appstore, despite that it is from 20 Nov.

[joseams86]

I found a solution and it seems to work without problems (chrome browser)

Download the version 1.0.3 of forms.
https://apps.nextcloud.com/apps/forms

Copy the "js" folder and paste it in: /nextcloud/apps/forms

To the forms.js and survey.jquery.min.js files change the owner to httpdusr (if you don't do this step you will not be able to see the forms when you save them.

Refresh the browser with cnrt. + F5 or restart it (windows)

That is all. I hope it works for you, it works for me.

[JazMTaz]

Same for me here NC 17.0.3 with PHP Version: 7.3.14 and Forms app version 1.1.0

[MaxG-Git]

would love to see a fix to this of possible
*edit: spelling error

[jotoeri]

@pzehle @mokkin
Can you provide some information on your setup?
How did you build from Master? (dev-setup, build-js-production?)

And just to be sure you know about: In current master you have to press Enter on Keyboard to add options.

Greets,
Jonas

[pwepwe973]

Same problem here. It doesn't seem to be solved.

I have the same problem for 2 months and from what I understood it is not nearly solved

[schniepp]

Awesome, it seems like v 1.1.1 fixes the issue! Thank you so much for moving this forward!

[rhersel]

Same problem for me on NC 17.02. Forms 1.1.0

[DBJRdev]

@joseams86 Thanks for the suggestion, but I was not able to reproduce your temporary solution. You meant just overwrite the same-name files or to replace the entire "js" folder (==deleting the other files in "js")?

[githubDante]

@joseams86 Thanks for the suggestion, but I was not able to reproduce your temporary solution. You meant just overwrite the same-name files or to replace the entire "js" folder (==deleting the other files in "js")?

forms.js and all files from the js/chunks/ dir. That's what is build by make build-js-production. It is better to clone this repo and to build from master. It takes several minutes and will work, unless you share forms publicly :-)

[agentlibre]

Same problem. Tested from multiple computers and different browsers.

[forteller]

I updated to the latest version, 1.1.6, yesterday, but that did not help.

[DBJRdev]

@forteller : Are you possibly mixing up "Forms" and "Polls", because there seems to be no new Forms version, but Polls actually has received an update yesterday or so.

[forteller]

Ah, yeah, that's correct. Sorry. No wonder I still have the same issue then :P

[agentlibre]

Could someone bring this issue to a higher priority? I am trying to prove the efficiency of the NextCloud environment to an association on the national level and this feature was exactly an important point I wanted to make... Please help :/

[peetCreative]

The author @ordaolmayanadam of PR #123 made more changes, which didn't came in the PR.
Maybe one also has to keep line 128 in Create.vue account?
<input id="unique" v-model="form.event.unique" :disabled="form.event.access === 'public' || form.event.isAnonymous">

I have no experiences with nextcloud apps. Just now try to manually build it.
Did not succeed by now. Maybe someone else is faster.

[nightbluepn]

@peetCreative you need to build it on your server/within the nextcloud file tree. i.e. clone this repository into apps/forms within your nextcloud directory, at least this is how i did it.

Adding answers is working with a current build, it still gives a db error on saving the form though.

[peetCreative]

Jup, I'm just stuck in an npm error, write access error, ...
I'll come back later.

[pwepwe973]

hello, still no solution for this bug?
an update is planned?

[pwepwe973]

hello
It's good i put the comment

[mokkin]

Unfortunately I'm facing the same issue even at the actual master https://github.com/nextcloud/forms/tree/07f9e4bdd5b83f36c5ec8b739585d12bc196b950

[pzehle]

Same problem here. It doesn't seem to be solved.

[pzehle]

@jotoeri hi, thanks for the reply.

Nextcloud version is 18.0.1
Forms version is 1.1.0

I installed Nextcloud as instructed from the website. Forms was downloaded directly from the nextcloud app store.

I don't think my setup could be any different from the many other users that have the same problem. Simply hitting enter to add an answer won't work.

[githubDante]

@pzehle
Yes this is a known issue. The version published to the app store does not include all commits to the master branch of this repo. Clone the repository, follow the production build instructions, then copy forms.js and all files which will be generated in the js/chunks dir to your installation and you will be able to add answers.

[pwepwe973]

yessssss for me too thank you

[DBJRdev]

Cool, it works with v1.1.1, thanks for the progress! I think we can close the issue now.

[pzehle]

Hello. Sadly it destroyed the app for me. I updated to v1.1.1, and as an admin I am able to open the app, but not even click on "new form", because I get this error:

As a regular user I am not even able to open the app, as it just redirects me to my root domain.

I tried uninstalling and reinstalling but still the same. Hope you can help me. Thanks.

[DBJRdev]

@pzehle : Hi, it seems that your problem is another issue. I would propose to open a separate issue for that, because developers might not find your problem here.

[born2webdesign]

Thank you for 1.1.1!

[br608]

Answering options cannot be added in v. 1.1.1. - in Safari I can add the answer, but not in Firefox, Edge or Chrome.