Our organization recently upgraded Confiforms from 2.18.13 to 3.5.8. It is causing a lot of tableviews stop working.
Form definition:
There is a field definition called category (drop down type: i.e 1:Cat1, 2:Cat2, etc.)
Table view:
Set values as key=value pairs, separated by & (as request parameters) for inline 'Add':
we used to set it as "category=1" without including a field in the tableview directly and it worked fine. However, after the upgrade, it stopped working unless we add the field of "category" in the tableview.
What it means is that:
- If we do not include the field "category" in the tableview, when we add a new record inline, it won't set the category=1 automatically.
- If we add the field into the tableview, then it sets the category correctly as 1
- Before the upgrade, we didn't have to include this field in the tableview because we wanted to hide it and automatically set it. But after the upgrade it stops working.
Can you please help provide a direction how we should fix it?
Thanks,
Sorry about that. This is a confirmed (now) regression - will provide a quick fix as part of the 3.6.1 version release
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.