Closed (fixed)
Project:
YAML Form
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Jun 2016 at 00:17 UTC
Updated:
10 Jul 2016 at 13:14 UTC
Jump to comment: Most recent
Comments
Comment #2
jrockowitz commentedI will absolutely look into this issue.
If you have a second free can you confirm this issue is also happening using simplytest.me. It would help to know if this truly module is broken or it is broken when installed with another contrib module.
Btw. Please make sure to clear your cache.
Comment #3
jrockowitz commentedI am seeing the below error message in the JavaScript console but it is not completely showstopping to the dialogs.
What browser and Drupal version are you using?
Comment #5
jrockowitz commentedI committed a simple fix to 8.x-1.x which will be available via the 8.x-1.x-dev release.
Please test it ASAP, so that I can push a new working release.
Thanks for reporting this issue.
Comment #6
SoYeah commentedI am using Drupal 8.1.3
Browser Tests with
Safari 9.1 and FF 47
will try it on simpletest and reply then
Comment #7
jrockowitz commentedYeh, I am using Chrome which can be more forgiving of JS errors, which is why I missed the error.
Comment #8
SoYeah commentedI tried the 8.x-1.0-beta5+5-dev on my hosting and on simpletest with standard install.
The error is still there.
Maybe this helps?
Fatal error: Unsupported operand types in /home/rric8/www/modules/yamlform/modules/yamlform_ui/src/Controller/YamlFormUiElementController.php on line 74
Thanks for your fast reply, if it works it will be awesome easy form building.
Comment #9
jrockowitz commentedThe error message is very helpful. I still can't replicate the issue locally or on simplytest.me.
The error is indicating that the YamlFormElements are not fully loading, which is really strange.
For reference, here is the file that is associated with the error. http://cgit.drupalcode.org/yamlform/tree/modules/yamlform_ui/src/Control...
I am hoping someone else can replicate this issue.
Comment #10
SoYeah commentedI just got the idea to switch it to the standard language (en) - my other testings where with German Settings.
Everything works fine, if I delete the translation of the example forms (wich are added on install), fields can be added through the UI.
Maybe this should be fixed for users in other languages than en/us.
Comment #12
jrockowitz commented@SoYeah, That was the issue!!!
I am only testing things in English, which is not usually a problem but these few lines of code were not being properly translated.
I committed a fix and gave you commit credit for helping me find and resolve this major bug.
Please review.
Comment #13
SoYeah commented@jrockowitz
Works like expected! Thank you!
One thing to know, maybe to be written in the read me:
If one will install the module with 2 (or maybe more) languages enabled, you will need to delete translations of example forms to add elements to them.
If you create a new form, then the hint is given on the translation page.
Comment #14
jrockowitz commentedI created the below ticket to address the translation issue.
#2755883: Improve Translations handling and documentation.