railer
Member
I’ve run into a perplexing issue on a Joomla 3.8.8 site with Fabrik 3.8.1.
We have a series of multi-select checkbox questions which are displaying the word “true” in lieu of the actual checkbox label. I've confirmed that instead of the assigned values for each checkbox option, the word "true" is being stored in the db.
I could use some input or feedback regarding why this is happening and how I might fix it?
FYI — This is a long 3 page form comprised of… surprise… 3 tabbed sections.
The first section — is a Contact Info section which is prefilled by the user’s contact info submitted in a separate form which also registers them in Joomla.
The second section — has straightforward questions and answers.
The third section — which pertains to this issue — has questions, many of which have custom calc elements which turn the labels text from questions into statements text in the Detail View. It also has code in it which hides the questions which the user did not answer. In essence the calc element is calling a function stored in the /includes directory. The statements are just rewording, basically. In the third section, there are 9 groups, each of which has one of these custom calc elements.
When we view any record’s Detail View on the front-end, in the third tab (section), the multi-select checkbox options are displaying the value “true”.
When we view any record’s Detail View in the backend via Lists/mylist/Edit, the multi-select checkbox options labels do display under the element Label and then are followed by the various “true” values.
I’m hoping you can tell me where these “true” values are coming from and why they are being stored in the database instead of the checkbox option labels?
I've uploaded a couple of files which show you how the detail view displays in the frontend (without checkbox labels), and in the backend (with checkbox labels). Note how the "true" values in the backend display under the actual checkbox values. To me it looks like they are just flowing into the space under their parent element since we didn't code them to be there.
Hope this explanation makes sense.
Thanks!
We have a series of multi-select checkbox questions which are displaying the word “true” in lieu of the actual checkbox label. I've confirmed that instead of the assigned values for each checkbox option, the word "true" is being stored in the db.
I could use some input or feedback regarding why this is happening and how I might fix it?
FYI — This is a long 3 page form comprised of… surprise… 3 tabbed sections.
The first section — is a Contact Info section which is prefilled by the user’s contact info submitted in a separate form which also registers them in Joomla.
The second section — has straightforward questions and answers.
The third section — which pertains to this issue — has questions, many of which have custom calc elements which turn the labels text from questions into statements text in the Detail View. It also has code in it which hides the questions which the user did not answer. In essence the calc element is calling a function stored in the /includes directory. The statements are just rewording, basically. In the third section, there are 9 groups, each of which has one of these custom calc elements.
When we view any record’s Detail View on the front-end, in the third tab (section), the multi-select checkbox options are displaying the value “true”.
When we view any record’s Detail View in the backend via Lists/mylist/Edit, the multi-select checkbox options labels do display under the element Label and then are followed by the various “true” values.
I’m hoping you can tell me where these “true” values are coming from and why they are being stored in the database instead of the checkbox option labels?
I've uploaded a couple of files which show you how the detail view displays in the frontend (without checkbox labels), and in the backend (with checkbox labels). Note how the "true" values in the backend display under the actual checkbox values. To me it looks like they are just flowing into the space under their parent element since we didn't code them to be there.
Hope this explanation makes sense.
Thanks!
Attachments
Last edited: