nickhead wrote: Turns out I

nickhead — Tue, 07 Apr 2009 21:37:40 +0000

nickhead wrote:

Turns out I misread the original instructions and butchered the url structure of the link to the redirected page. Whyyy it only didn't work in Safari is beyond me. But Safari is a jerk in general, so it makes sense.

I figured it out - thanks guys.

nickhead wrote: it's the

greg — Tue, 07 Apr 2009 20:56:02 +0000

nickhead wrote:

it's the redirect that was busted in Safari.

You'll have to show us some code to help you there (unless someone knows of a known issue with Safari and redirect)

That said, I would guess that's not likely to be a browser specific issue, certainly not on its own, and more likely to be something else.
Such as editing redirect code and re-testing but not clearing the browser cache, or perhaps you have a plugin/extension that s fouling the redirect.

Hey Thanks guys. I should

nickhead — Tue, 07 Apr 2009 20:28:14 +0000

Hey Thanks guys. I should have been more specific - the form itself works fine, it's the redirect that was busted in Safari.

Thanks! I really appreciate you guys taking a look.

form works okay by itself in

decibel.places — Tue, 07 Apr 2009 18:53:24 +0000

form works okay by itself in Safari for Windows (see attached)

maybe it has something to do with the container as greg suggested

as a matter of style I would write the FORM tag on a single line, although I do not think it matters functionally:

<FORM METHOD="POST" ACTION="http://printnetinc.com/cgi-bin/cgiemail/checkout/formtemplate.txt">

(Yours breaks after "POST")

** you get an error msg if the first name is not entered - you should have some better validation process that doesn't "break"

I can't help you "directly"

greg — Tue, 07 Apr 2009 18:01:00 +0000

I can't help you "directly" with the issue with Safari (I don't run it on my OS), but having the entire form in one table cell is a bit of a weird approach.
(It "may" be the reason it doesn't work well in Safari)

There are better ways to approach this with CSS forms, but even having each input (name, address etc) as one table row would be better.