I'm using Chronoforms 1.3RC 5.5. All is working wonderfully well. :-)
I'm looking after a school website, which has a Chronoforms enrolment form. Anyhow it was working using PHP mail, then we discovered it had stopped working....We switched to SMTP and got it working again. (So Chronoforms was never the problem it was an issue on GoDaddy the hosting site).
My Question is this, is there anything I can do so that if it happens again I do not "Loose" any forms that people may have submitted? Is there a way to track submissions? I hate to think that people may be thinking they've enrolled their kids in the school and the school knows nothing about it. Even if I could track the emails or any field from the form that would be super.
Many thanks for any suggestions you can offer.
p.s. I'm a total novice at this, so sorry if answer should be obvious.
Hi Esthalon ,
Yes, for sensitive forms (that's many of them) you should enable a DB Connection to save the form data to a database table in case something like this happens.
Bob
Thanks Bob, I created a table and linked it to the from as per your Tutorial, "Saving Data to the Database". When I complete and submit the from now, it generates a record in the table so I'm almost there😀
However, the screen shots in the Tutorial "Create the Table 2" don't exactly match my version of Chronoforms (3.1), so I may have gone wrong here. When I view the record I see cf_id etc, but do not see any of the data from the completed form e.g. email address, name etc. (Like in "viewing the record" in the tutorial).
Can I manually add some fields so they are recorded/viewable?
Hi Esthalon,
The tutorial is from a previous version and needs updating - maybe one day.
You can add columns manually with PHPMyAdmin or using the ChronoForms Tables Manager | Edit dialogue (Click the green + icon to add an extra column). Or, if you only have test data saved delete the table from the Tables Manager and re-create the table but this time click the x icon in the blue bar to turn all the bars green. (Or the x/tick icon on individual bars to add or remove them).
Bob
Thanks I'll give it a go tonight.
Hi Bob,
I got it all working, thanks for helping me out.
A little feedback in case anyone else is in the same situation...
I didn't initially realise that the Table Manager under Chronoforms listed all the tables for my website (I only look after Joomla side of things soemone else set it up on hosting site, so initially I was wondering where all these tables had come from and if they were important!!!)😶
When hovering over the red x in table manager the tip is "enable/disable"....it wasn't immediately apparent to me that this is how you delete the table. As whenI clicked on it I got a green tick indicating enabled, so I kept cancelling out as I was expecting a "Delete" tip or at least to be going from Enabled to Disabled, not Disabled to Enabled.
I hope that makes sense and might save someone else a bit of time....or maybe I'm just a bit braindead at this hour.
Anyway thanks again to Bob, for his super fast support!
I spoke to soon! All went fine in testing, in completing my form I was supplying my work email address.
But issues were reported and upon investigation it seems if someone completes the from with a valid gmail address they get an error, I tested with my gamil account and got PHPMAILER_FROM_FAILEDjune.p.doyle@gmail.com AND if I try to complete my form with a valid yahoo email address it doesn't even get that far, the form will not submit at all it tells me the [email]name@yahoo.com[/email] email address is invalid.
Any ideas?
Sorted. I stoppped using dynamic from email field in email setup and am just using a static one specifying the webadmin account. Not as flash, but it seems to be infinitely more reliable.
Hi Esthalon,
I strongly recommend that you do *not* use the Dynamic From Email element in your Email Setups. Using this often results in your emails being marked as spam and dropped into a spam filter. Instead use the static From Email with an address that matches the site domain name and use Dynamic ReplyTo Email for the user email. The result is the same but with a much better chance of good delivery.
Bob