In Umbraco 7.5.9 (and 7.5.9) i've encounter the following issue:
When saving my form, checkboxes are always posted as False
When viewing the record inside Umbraco, the values are False
When retrieving the field value, the value is False.
The recorddata in table UFRecords also shows json with false values for checkboxes
Example data in the database:
{'183fba08-5ed2-4a1a-8cc1-3364b0529e7e':'item 1, item 2','aec143aa-806c-43dd-9289-f9bcfb76065d':'False','eb357878-54cb-4a44-ba42-74959fd5b1cd':'False','a3491195-de34-47a9-dc1e-8bc5911dc604':'10-7-2018 00:00:00','7a19dfa1-98cb-4a08-b719-7fb5e96ea681':'Input 123','629e6d2f-10fd-4564-c6fc-30efc68ceb7a':'','f450c3ab-7fdd-4cc7-c246-d1171f4b983b':'No'}
Love to hear a working solution!
Tried upgrading to Umbraco Forms 4.4.7. After the second attempt I managed to get it working. Also running the package created by Tim helpt:
https://our.umbraco.com/forum/umbraco-pro/contour/60744-Entries-have-dissappeared#comment-206075
After restoring my bootstrap markup, new and old Umbraco Form were working again.
Related
The form in 2017.1 looks OK:
When I use the formrunner home to push the published form to 2017.2.1, the form also looks OK:
When I took the source from 2017.1 and insert it in the 2017.2.1 formbuilder,
the form in the formbuilder also looks OK:
But using the test key to preview the form, the fields are cluttered. Also if I publish the form and look at the published form.
Link to the used xhtml source code in orbeon 2017.1
What is the right way to port forms from 2017.1 to 2017.2.1?
Many thanks for every guide and hint
I do reproduce the issue. The problem is that with Orbeon Forms 2017.2, Orbeon Forms switched the way it represents grids. Grids now always have 12 columns. This means that grids previously created with 1, 2, 3, 4, 6, or even 12 columns adjust perfectly.
But grids with 5 columns, like your second grid, are just handled as having 5 rows in a 12-column grid, and so they don't look like before.
A workaround is to make the grid have 6 or 4 columns (<xh:td>) in the source instead.
Is it possible to unbind event for adding xforms-visited class to specific element of form?
I have one collapsible section (initially closed) with only one paragraph and I need it to remain closed after validation, but it gets xforms-visited and fr-section-open classes if something on form doesn't pass validation. Maybe it could be also related to binding opening sections if data on form is invalid.
FYI - I'm using Orbeon 2016.3 version
Orbeon Forms 2018.1 and newer only expands sections that contains errors. This is done with the new expand-invalid action.
Until Orbeon Forms 2017.2, all the sections expand when an error is encountered.
I am using displaytag with struts 2 in my project, The problem is that displaytag pagination doesn't seem to work. The link generated are like
javascript:displaytagform('userListForm',[{f:'page',v:'2'}]) but when I click it the page parameter is not passed along with the request. It is not creating the hidden field page to store the page value, but if I add ?page=pagenum to the URL once, then the hidden field is created and afterwards it works fine. My question is why it is not creating the field for the first time itself.
I'm trying to troubleshoot a bug in my application. I have a form on a page with two fields: a textbox and a checkbox. I'm submitting this form via ajax using :remote => true and displaying the results on the page.
In some cases - even though the checkbox is checked - the console log shows the value as empty.
It looks as though this happens consistently after the first time the form is submitted.
I'm having a hard time tracking down why this could be happening.
Any ideas on where to start investigating would be much appreciated.
I think I sorted this out. On the create.js.erb I was setting the attribute of the checkbox to not checked. I was doing this to reset the form instead of $('#someid > form')[0].reset(); I just changed that out and it seems to be working as expected on each subsequent post.
I've got an MVC app that gives the user textarea's to update some description fields. It's strongly-typed to a table object, and the fields are wrapped in a form with a Submit button.
Occaisionally they don't want any data in a field, but when they delete the text and try to save, the blanked-out field comes back with its original text (i.e. the table object passed to the Save action contains other edits, but attempts to blank out fields result in the original text staying in the field).
I'm assuming this is LINQ trying to determine which fields have been edited, but how do you tell it that it's blank on purpose?
UPDATE: It appears this may be a problem with the TinyMCE jQuery plugin. It adds rich-text functionality to textarea controls. If I turn it off, I can remove text with no problems.
UPDATE 2: It seems to be some kind of javascript bug or something. If I put another dummy field after the problem fields, they work. If I move them to another place in my code, they work. They just don't want to work where they are. Very peculiar.
I'm pretty sure that TinyMCE, by default, puts in <p></p> when the control is emptied.
So if you are checking for "" then you may be disapointed.
This initially caused me some issues but never with saving. I was checking if the field was "" and then doing something else. Once I realised that "" was never going to happen, I adapted my validation accordingly.
I just check that on a recent project using TinyMCE editor, but it indeed send "" for an empty input, and during the implementation we had no issues with that.
alt text http://diarioplus.com/files/pictures/tiny.PNG
The body property is the one with a tinyMCE editor on the client side.
I really think it will be something with the modelBinder or the way you set the values back to the model.