VOI
Member
Hi,
I am currently in the process of preparing the migration of my major client side from J!2.5 to J!3.2. I really like the new bootstrap design and found a lot of great improvements in Fabrik. This is really a major step forward. Great job guys!
While some of the bugs reported for Fabrik 3.0.9 are gone in 3.1rc2, there are some new ones as well. I will post those in this and my following threads.
First one is about databasejoin elements. They are showing the value (in my case the id) instead of the label (in my case a user name) after a validation rule failed - and if the element is read-only due to Access settings of the element. Before the failed validation the element was showing the label just fine.
I didnt change any of the settings of the corresponding databasejoin elements after migrating from J!2.5. The same error occurs with new databasejoin elements created after the migration.
Chris
I am currently in the process of preparing the migration of my major client side from J!2.5 to J!3.2. I really like the new bootstrap design and found a lot of great improvements in Fabrik. This is really a major step forward. Great job guys!
While some of the bugs reported for Fabrik 3.0.9 are gone in 3.1rc2, there are some new ones as well. I will post those in this and my following threads.
First one is about databasejoin elements. They are showing the value (in my case the id) instead of the label (in my case a user name) after a validation rule failed - and if the element is read-only due to Access settings of the element. Before the failed validation the element was showing the label just fine.
I didnt change any of the settings of the corresponding databasejoin elements after migrating from J!2.5. The same error occurs with new databasejoin elements created after the migration.
Chris