Support Forums

This is a script i was working on and could not work out the problem.
Basically its simply a quote form of sorts. But works fine in FF but not in IE8?
Now i have taken away all the html crap and posted only the code as i think this is where the problem lies. Well im sure of it actually.

Simple enough.

Now for the processing part.


Once again no big deal. Just processing a quote and echoing the result.
Now what i tried to do next is once the form had been processed it produced not only the above result but also a couple of buttons to further navigate. This is where the issue is.


Now please dont bash me on this thread. I am the first to say i know bugger all about php and my code is messy..

EDIT

Sorry i should add. The problem was the buttons would show up but not do anything in IE8 but in FF they work fine.

(10-13-2009, 02:31 AM)DAMINK™ Wrote: [ -> ]<?php
$Colors = $_POST["Colors"];
$quantity = $_POST["quantity"];
$size = $_POST["size"];
?>
[/php]

Did you forgot the quotes.....

What error are you getting in IE, do you get any errors?

No errors. And the code you see is what i used actually.
The only problem is the script would run and produce the result but when the buttons appeared they would not do anything.
In FF they work fine. I mean the "back" button and the "Process Order" buttons.

I didn't found any error in the coding. may be IE not compatibility issue :-/

Yes thats what i put it down to also immi.
Still my client did not accept that. There answer was "well 99.9% of the net use IE8" lolol.
I had to inform them actually only 13% do and nearly 50% use FF but still the script failed and i looked quite the fool.
For the site in question i simply used a text link to replace the buttons in the result and that works in ie.

(10-13-2009, 02:41 AM)DAMINK™ Wrote: [ -> ]I had to inform them actually only 13% do and nearly 50% use FF but still the script failed and i looked quite the fool.

Only 13 % ? IMHO might some 70 + % people love to use IE 8

(10-13-2009, 02:31 AM)DAMINK™ Wrote: [ -> ]

PHP Code:

if ($size == "a4") echo "<a href='processor1.php'><input type='button' action='/' name='Process Order' id='Process' value='Back'></a>"; 


Yes the errors is within those lines, for IE this is an invalid code and IE doesn't know what to do with it.
I either recommend you to use <a> and style it with css as an button or to use only button, both are not good, not even for FF even tought it works.

I still recommend using the anchor tag only and put <img> of the button or use <div> inseda of <a> and style it with css

edit:
You shouldn't insert <input> inside <a> tags, that's the same as

http://www.w3schools.com/browsers/browsers_stats.asp
Thats where i got my stats from actually.

---

(10-13-2009, 02:52 AM)NinjaGeek Wrote: [ -> ]Yes the errors is within those lines, for IE this is an invalid code and IE doesn't know what to do with it.
I either recommend you to use <a> and style it with css as an button or to use only button, both are not good, not even for FF even tought it works.

I still recommend using the anchor tag only and put <img> of the button or use <div> inseda of <a> and style it with css

Code:

background:rgb(212,208,200);
border-top:2px solid rgb(255,255,255);
border-left:2px solid rgb(255,255,255);
border-right:2px solid rgb(128,128,128);
border-bottom:2px solid rgb(128,128,128);

Yea i was going to use an image with a link but got pretty pissed off with client. Told them to stick the job up there ass lol.
Put a text link there and then signed off on the job. It was more just for curiosity regarding the problem.

DAMINK™ Wrote: [ -> ]Yea i was going to use an image with a link but got pretty pissed off with client. Told them to stick the job up there ass lol.
Put a text link there and then signed off on the job. It was more just for curiosity regarding the problem.

The problem is that you are using two types of almost same types of tags inside each other.
You could also create for every button new form and set buttons to submit and leave the anchor tag out of the lines, that would also solve the problem.
But never put input tags inside anchors, or vice versa.

Ahhhh good call Ninja. Cheers for that mate.