I have found a bug in Fabrik4(delta) for the JDate element used read only in a Fabrik form. The forms work fine in J!3 & Fabrik3.10. Apologies if this is reported already, but I could not see it searching manually in this forum.
If you have a list with a JDate element that is displayed read only in an edit form, then upon saving the row the JDate field is NULLED out in the database.
The JDate element is configured to display in "Y-m-d" format. And is made read only by setting Access:Form(edit) to "nobody".
This occurred in a more complex table structure with joined tables and several prefiltered lists onto the same tables but I isolated the problem down to the simple case described below.
I created a new List with a single jdate field. I added several rows to this table, and then switched the element's access to be editable by nobody (ie read only). On subsequent saves of rows the date field is nulled out in the database.
If you have a list with a JDate element that is displayed read only in an edit form, then upon saving the row the JDate field is NULLED out in the database.
The JDate element is configured to display in "Y-m-d" format. And is made read only by setting Access:Form(edit) to "nobody".
This occurred in a more complex table structure with joined tables and several prefiltered lists onto the same tables but I isolated the problem down to the simple case described below.
I created a new List with a single jdate field. I added several rows to this table, and then switched the element's access to be editable by nobody (ie read only). On subsequent saves of rows the date field is nulled out in the database.