Hi Bob! -- It's been a while :-)
I created a simple form with a file attachment. When I test the form via Test Form on CF control panel the form works great. When I test the form from the website's front end, it won't submit. I'm not doing anything different than I've ever done, so I don't know what's going on. Here are the respective URLs
Test Form
http://www.aaxon.com/index.php?option=com_chronoforms5&chronoform=SeekingLocations
Form on webpage
http://www.aaxon.com/laundromat-locations
Thanks in advance for your help!
Jose
I created a simple form with a file attachment. When I test the form via Test Form on CF control panel the form works great. When I test the form from the website's front end, it won't submit. I'm not doing anything different than I've ever done, so I don't know what's going on. Here are the respective URLs
Test Form
http://www.aaxon.com/index.php?option=com_chronoforms5&chronoform=SeekingLocations
Form on webpage
http://www.aaxon.com/laundromat-locations
Thanks in advance for your help!
Jose
Hi Bob,
There are a ton of CF forms on this website. All the other forms work fine. If it were SEF URL's, wouldn't the issue be on the other forms as well?
I tried placing the form on a hidden menu item (http://www.aaxon.com/seeking) but it's still not working.
Jose
There are a ton of CF forms on this website. All the other forms work fine. If it were SEF URL's, wouldn't the issue be on the other forms as well?
I tried placing the form on a hidden menu item (http://www.aaxon.com/seeking) but it's still not working.
Jose
Hi Jose,
That's still my best guess - the form submits correctly without the template and from the full CF URL
Bob
That's still my best guess - the form submits correctly without the template and from the full CF URL
Bob
I FOUND IT! -- The form's name was "SeekingLocations" -- It noticed all other forms were all lower case. I changed the form's name to "seekinglocations" and it solved the problem. Go figure...
Thanks!
jose
Thanks!
jose
Hi Jose,
I'm not sure what the problem was - form names are case sensitive. Maybe there was a menu that had the 'wrong' version set.
Bob
I'm not sure what the problem was - form names are case sensitive. Maybe there was a menu that had the 'wrong' version set.
Bob
Hi Bob,
The form was called "SeekingLocations" but the client had it on the article as {chronoforms5}seekinglocations{/chronoforms5}. If the names are case sensitive, it's interesting that the plugin would still display the form.
Best regards,
Jose
The form was called "SeekingLocations" but the client had it on the article as {chronoforms5}seekinglocations{/chronoforms5}. If the names are case sensitive, it's interesting that the plugin would still display the form.
Best regards,
Jose
This topic is locked and no more replies can be posted.