I seem to be having a problem with a simple Form redirect.
You can click the Submit button on my Mac and it redirects to the page just fine however when you try it on the PC it doesn’t work. The Reset & Submit buttons I copied from a previous form don’t seem to want to work.
Could you post a link to the trouble page? What method are you using
for your form, and what type of form handler?
Walter
On Jul 26, 2010, at 3:59 PM, Clark Brown wrote:
I seem to be having a problem with a simple Form redirect.
You can click the Submit button on my Mac and it redirects to the
page just fine however when you try it on the PC it doesn’t work.
The Reset & Submit buttons I copied from a previous form don’t seem
to want to work.
You probably don’t want to hear this but it is hosted by GoDaddy and I use their gdform.php script. I Post to this in the Form Setup box. It has been working fine with other forms like this one for years. Troublesome.
Clark,
On your submit button can you remove the “blank” or space and retry?
Your value="Submit " is like this. IE probably does not like that space you have after after Submit. Maybe could you also add name=“Submit” as well with this.
Could you point to a form page you have made on the same server that did work? I have a theory here, based on what I see in the “name” attributes of your form elements.
When handling a form by PHP, I believe you have to follow the same rules for naming your form elements that you do when creating a variable in PHP itself:
A variable must begin with an alphabetical character in the US ASCII range (basically a-z or A-Z).
A variable name may never contain any spaces or dashes or any other punctuation except the underscore character.
You have loads of form elements here with spaces and punctuation in their names, and quite probably some beginning with numbers. I would be very surprised if this worked at all, on any PHP form handler, let alone with GoDaddy.
Note carefully that in Freeway, when you have selected a form element, the first tab of the Inspector shows a field called Title. This is not the same thing as the Name attribute, which is all that your form handler will ever look at or care about. The Name attribute is set either on the right-most or second-to-right-most tab of the Inspector (depending on the context of your element).
Also, names must be form-unique, just like IDs on the page, unless you are dealing with a group of checkboxes or radio buttons. If they are not unique, then your handler will receive multiple values for the same variable name, and the last one will “win”.
Walt,
Here is a form that is working. I actually copied the fields
here and modified these to suit this particular form. This has always worked fine in the past.
Walter,
I am sorry to have wasted your valuable time. I found the source of the problem. On that page I had a Constant Contact Join our email list sign up box. I deleted it from the page and everything works now. The code must have been conflicting
with the form somehow.
If you had pasted some code from Constant Contact on the page, you
might have ended up with a form inside a form, which is not valid HTML
(and gets very confusing for the server, too). Freeway will, by
default, put its form tags outside of anything else on the page, which
makes it impossible for you to add another form to the page without
ending up in this hole. In order to have multiple forms on a single
page, there is an Action called Multiple Forms. You apply the first
part to the page (I think it’s called Remove Form or No Form) and then
you have to apply the other part to an HTML box or table that entirely
contains the form elements. This moves the form inside the page and
puts it under your control as far as the source order goes, and makes
it possible to have one form pointing to CC and another pointing to
your contact handler.
Walter
On Jul 27, 2010, at 2:34 PM, Clark Brown wrote:
Walter,
I am sorry to have wasted your valuable time. I found the source
of the problem. On that page I had a Constant Contact Join our email
list sign up box. I deleted it from the page and everything works
now. The code must have been conflicting
with the form somehow.