I try to use the Rating, from the advanced fields, but I get the results only in the email, they are not stored in a database field. Any ideas? (all the other answers from other fields are saved correctly in the DB). I use the Save Data option.
Forums
Rating not stored in DB
Hi rethtourism,
Please turn debug on in the form General Tab, then submit the form and post the debug results here.
Bob
Please turn debug on in the form General Tab, then submit the form and post the debug results here.
Bob
As you see the rating info exists in the email, but not in the db
Array
(
[option] => com_chronoforms6
[cont] => manager
[chronoform] => sygatathesi
[event] => submit
[name] => ghfghfgh
[class] => 12
[parentname] => κλξκλξλκξκλ
[parent] => Πατέρας
[calendar17] => 2020-05-08 17:25:00
[sygatahesi] => 1
[rating26] => 4
[button7] =>
[_ga] => GA1.2.1913346487.1581968855
[jSGCacheBypass] => 1
[c9995d7e98ca201d7bd107347eda0096] => 68cc800f82291e9a629da91523003b76
[398ace724d30c36b9a6d46346e8a0e42] => 1
)
Array
(
[submit_validate_fields] => Array
(
[log] => Automatic validation enabled.
[var] => 1
)
[validate_fields2] => Array
(
[log] => Automatic validation enabled.
[var] => 1
)
[save_data8] => Array
(
[data] => Array
(
[created] => 2020-05-08 14:25:31
[user_id] => 42
[name] => ghfghfgh
[class] => 12
[parentname] => κλξκλξλκξκλ
[parent] => Πατέρας
[calendar17] => 2020-05-08 17:25:00
[sygatahesi] => 1
)
[_success] => Data saved successfully
[log] => Array
(
[0] => INSERT INTO `K96by_chronoforms_data_sygatathesi2` (`created`, `user_id`, `name`, `class`, `parentname`, `parent`, `calendar17`, `sygatahesi`) values ('2020-05-08 14:25:31', '42', 'ghfghfgh', '12', 'κλξκλξλκξκλ', 'Πατέρας', '2020-05-08 17:25:00', '1');
)
[var] => Array
(
[created] => 2020-05-08 14:25:31
[user_id] => 42
[name] => ghfghfgh
[class] => 12
[parentname] => κλξκλξλκξκλ
[parent] => Πατέρας
[calendar17] => 2020-05-08 17:25:00
[sygatahesi] => 1
[aid] => 373
)
)
[email5] => Array
(
[recipients] => Array
(
[0] => 2dimrethymno@gmail.com
[1] => 2dimreth@sch.gr
)
[subject] => Συγκατάθεση Γονέα
[body] => <table width="100%" cellpadding="0" cellspacing="0" border="0" class="" style="border:3px solid #e2e2e2; border-collapse:separate; border-radius:7px;">
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<h2 style="padding:0px 7px;"><center>Φόρμα γονικής συγκατάθεσης<br>για δημιουργία μαθητικού λογαριασμού στο Πανελλήνιο Σχολικό Δίκτυο</center><div class="sub header"><center><span style="font-size:14px;">Το σχολείο του παιδιού σας πρόκειται να δημιουργήσει λογαριασμό πρόσβασης<br>στην υπηρεσία Ηλεκτρονικού Ταχυδρομείου και στις υπόλοιπες υπηρεσίες του Π.Σ.Δ www.sch.gr/services</span></center></div></h2></td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;">Ονοματεπώνυμο Μαθητή/τριας</span></strong></td>
</tr>
<tr>
<td style="padding:7px;">ghfghfgh</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;">Τάξη/Τμήμα</span></strong></td>
</tr>
<tr>
<td style="padding:7px;">12</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;"><h3 style="padding:0px 7px;"><center>Δήλωση Συγκατάθεσης</center></h3></td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;">Ονοματεπώνυμο Γονέα</span></strong></td>
</tr>
<tr>
<td style="padding:7px;">κλξκλξλκξκλ</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;">Γονέας</span></strong></td>
</tr>
<tr>
<td style="padding:7px;">Πατέρας</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;">Ημερομηνία</span></strong></td>
</tr>
<tr>
<td style="padding:7px;">2020-05-08 17:25:00</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong><span style="font-size: 16px;color:#21ba45;"><b>Δηλώνω υπεύθυνα ότι επιτρέπω στον διαχειριστή μαθητικών λογαριασμών του 2 ΔΣ Ρεθύμνου, τη δημιουργία λογαριασμού του παιδιού μου και την ενεργοποίησή του, στο ΠΣΔ</b></span></strong></td>
</tr>
<tr>
<td style="padding:7px;">1</td>
</tr>
</table>
</td></tr>
<tr><td width="100%" style="padding:5px; border-bottom:1px solid #e2e2e2;">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr style="background-color:#fafafb">
<td style="padding:7px;"><strong>rating26</strong></td>
</tr>
<tr>
<td style="padding:7px;">4</td>
</tr>
</table>
</td></tr></table>
[result] => the Mail sent successfully.
[var] => 1
)
)
Hi rethtourism,
Is there a rating26 column in the table? If there is, please try clicking the ChronoForms Clear Cache button and see if that fixes the problem.
Bob
Is there a rating26 column in the table? If there is, please try clicking the ChronoForms Clear Cache button and see if that fixes the problem.
Bob
the rating26 field value is not passed to the save data which means a problem somewhere, you can force its value in the data to be saved using the "Data overrides" in the "Save data" settings, make sure your table has a field named "rating" or whatever and add the following override:
rating: {data:rating26}Best regards
Thanks guys
I force it to include the rating data in the 'create table' option and it ok now.
p.s.
By the way, I checked the chronoforms v.7beta, and as it is now it seems that MOST of the options are missing, compared to v.6.
And also the new environment seems worst (more poor, more complex, more ugly) than v.6
Sorry for these remarks...
I love you
I force it to include the rating data in the 'create table' option and it ok now.
p.s.
By the way, I checked the chronoforms v.7beta, and as it is now it seems that MOST of the options are missing, compared to v.6.
And also the new environment seems worst (more poor, more complex, more ugly) than v.6
Sorry for these remarks...
I love you
The v7 has "options on demand" principle, you will not have to experience any settings unless they are going to be used.
After it's ready we plan to have some videos to explain the interface, it's much easier than v6
Your suggestions are welcome on how to improve the interface!🙂
After it's ready we plan to have some videos to explain the interface, it's much easier than v6
Your suggestions are welcome on how to improve the interface!🙂
Thanx Max
The "options on demand" will be based on the purchase price or packet or on the needs for usage, independently of the purchase price?
In my humble opinion, (and as a fanatic follower of chronoforms for many many years, with various accounts) and in my discussions with many other web developers, one of the things we like in chronoforms is the big variety of options.
Maybe you can set different categorization of the options, like simple form, medium form, advanced form.
Another good idea would be to have the option of different colorization of the elements in the backend, which will make the reading of the parts of the forms, easier for the developers, especially for BIG forms with many elements.
And another good option would be to remove the dependence of the" Tag" to the 'Field Text" of an element. As I wrote to you in the forums via another account, the system accepts html styling (ex. <span style="color:#ff0000;font-size:20px; ">Field Text</span>), but it copies all this to the Tag of the element and this "breaks & destroys" the form.
I can use the chronoforms css option for the form parts (like background color or photo), but this css option does not affect the Field Text.
The "options on demand" will be based on the purchase price or packet or on the needs for usage, independently of the purchase price?
In my humble opinion, (and as a fanatic follower of chronoforms for many many years, with various accounts) and in my discussions with many other web developers, one of the things we like in chronoforms is the big variety of options.
Maybe you can set different categorization of the options, like simple form, medium form, advanced form.
Another good idea would be to have the option of different colorization of the elements in the backend, which will make the reading of the parts of the forms, easier for the developers, especially for BIG forms with many elements.
And another good option would be to remove the dependence of the" Tag" to the 'Field Text" of an element. As I wrote to you in the forums via another account, the system accepts html styling (ex. <span style="color:#ff0000;font-size:20px; ">Field Text</span>), but it copies all this to the Tag of the element and this "breaks & destroys" the form.
I can use the chronoforms css option for the form parts (like background color or photo), but this css option does not affect the Field Text.
the options on demand means that you do not have to have a huge list of config fields in your form fields, but just the minimum, anything needed can be enabled through a behavior, this has nothing to do with purchasing!
I could not understand the colorization idea, an image can make it easier🙂
The html code breaking the label is on the to fix list
Best regards
I could not understand the colorization idea, an image can make it easier🙂
The html code breaking the label is on the to fix list
Best regards
Dear Max
Thanks for the clarification.
I attach you a photo to show you what I mean with the coloring of areas, elements, etc in the backend.
It would also be a good idea to have the option to save data (Save to DB) in a google sheet. There is a paid plugin from a guy from Australia, that seems to work fine. I also think that in v.5 there was such an option, but not in v.6.
coloring of areas, elements, etc in the backend.
Thanks for the clarification.
I attach you a photo to show you what I mean with the coloring of areas, elements, etc in the backend.
It would also be a good idea to have the option to save data (Save to DB) in a google sheet. There is a paid plugin from a guy from Australia, that seems to work fine. I also think that in v.5 there was such an option, but not in v.6.
coloring of areas, elements, etc in the backend.
sorry for the repetitions of the texts, in the previous message, it was mistake
No problem!🙂
Thank you for your suggestions, hopefully v7 will be a better experience for you and other Chronoforms users!
Thank you for your suggestions, hopefully v7 will be a better experience for you and other Chronoforms users!
Dear Max
I hope you are well and you keep calm in these hard times.
I thought of another improvement for V.7.
Since chronoforms is a VERY powerful application, I believe it is important that the users will be able to take advantage of all of its capabilities.
But in many areas, there are some fields that are not clear as to what they do or what the developer should put in or even what kind of syntax should he use.
Examples: Container class, Extra attributes, Validation rules, Data values, Container class, Checked status provider, Reload event, Data value, Placeholder etc
It would be a good idea if there were tooltips (and even dropdowns) with information about the use of each field, the possible options, and their syntax. Or if there are rich information of every field options in the manuals, there can be at least tooltip links to the appropriate part of the manual.
I hope my ideas are not annoying to you and your hard work. If they are, feel free to ignore them.
regards
mik
I hope you are well and you keep calm in these hard times.
I thought of another improvement for V.7.
Since chronoforms is a VERY powerful application, I believe it is important that the users will be able to take advantage of all of its capabilities.
But in many areas, there are some fields that are not clear as to what they do or what the developer should put in or even what kind of syntax should he use.
Examples: Container class, Extra attributes, Validation rules, Data values, Container class, Checked status provider, Reload event, Data value, Placeholder etc
It would be a good idea if there were tooltips (and even dropdowns) with information about the use of each field, the possible options, and their syntax. Or if there are rich information of every field options in the manuals, there can be at least tooltip links to the appropriate part of the manual.
I hope my ideas are not annoying to you and your hard work. If they are, feel free to ignore them.
regards
mik
This topic is locked and no more replies can be posted.