Bit of weird one...
We've built a form for a client website, which was tested and found to be working when first built. It has since become a bit temperamental, and the submissions no longer get forwarded to us via email.
In frustration, I deleted the form on Tuesday afternoon and rebuilt it from scratch. It still wouldn't work, so I moved it from inside of a module to inside of a (K2) article - form still wouldn't send.
I turned the module beside my form module off (content-top-a & content-top-b, respectively), and the form began to work. I enabled both modules again, and the form still continued to work.
When I tested the form again this morning, it has stopped working again. Nothing has been done to the site since I discovered the form was working at the end of the day on Tuesday. At a total loss with this one.
The form can be found at http://111.223.236.34/~bigboys, and the CSS being used to style it is included below.
Anyone have any thoughts as to what the problem could be? There are about three other Chronoforms on the site, which are all working fine.
We've built a form for a client website, which was tested and found to be working when first built. It has since become a bit temperamental, and the submissions no longer get forwarded to us via email.
In frustration, I deleted the form on Tuesday afternoon and rebuilt it from scratch. It still wouldn't work, so I moved it from inside of a module to inside of a (K2) article - form still wouldn't send.
I turned the module beside my form module off (content-top-a & content-top-b, respectively), and the form began to work. I enabled both modules again, and the form still continued to work.
When I tested the form again this morning, it has stopped working again. Nothing has been done to the site since I discovered the form was working at the end of the day on Tuesday. At a total loss with this one.
The form can be found at http://111.223.236.34/~bigboys, and the CSS being used to style it is included below.
Anyone have any thoughts as to what the problem could be? There are about three other Chronoforms on the site, which are all working fine.
#chronoform_Quick-Enquiry .ccms_form_element {
margin-bottom: 0 !important;
padding: 0 !important;
}
#chronoform_Quick-Enquiry label {
font-family: YanoneKaffeesatzLight, Helvetica, Arial, sans-serif !important;
font-size: 18px;
font-weight: normal;
text-transform: uppercase;
}
#chronoform_Quick-Enquiry input {
width: 180px !important;
}
#chronoform_Quick-Enquiry #autoID-7b3ec05279c5787a0885204d76396353_container_div input {
background-color: #2358A6;
border: none;
border-radius: 5px 5px 5px 5px;
color: #FFF;
cursor: pointer;
float: right;
font-family: YanoneKaffeesatzLight, Helvetica, Arial, sans-serif;
font-size: 16px;
margin-top: 10px;
text-transform: uppercase;
width: 100px !important;
}
#chronoform_Quick-Enquiry #autoID-7b3ec05279c5787a0885204d76396353_container_div input:hover {
background-color: #252525;
-moz-transition: background-color 0.2s linear 0s;
-webkit-transition: background-color 0.2s linear 0s;
}
Hi aforantman,
Nothing about the form looks odd or problematic (couple of minor comments below). when you say it doesn't send emails how do you know? Is it saving data to a DB table OK?
Bob
Minor comments: (a) Using the auto id in your CSS can cause you problems if something changes; better to assign ids of your own choice in the form elements. (b) Dashes in form names used to cause problems, I think this is now fixed but I still avoid them.
Nothing about the form looks odd or problematic (couple of minor comments below). when you say it doesn't send emails how do you know? Is it saving data to a DB table OK?
Bob
Minor comments: (a) Using the auto id in your CSS can cause you problems if something changes; better to assign ids of your own choice in the form elements. (b) Dashes in form names used to cause problems, I think this is now fixed but I still avoid them.
This topic is locked and no more replies can be posted.
