How come IE can't parse PHP files that are parsed from HTACCESS to HTML. Without the page breaking ?
| SitePoint Sponsor |





How come IE can't parse PHP files that are parsed from HTACCESS to HTML. Without the page breaking ?
I can't help with the problem, but yes, IE is dumb for a lot of reasons.


Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.

You need to either upload the files containing the PHP to a server that supports PHP before you can use them or if you want to be able to test on your own computer you need to install a web server and PHP onto your computer so as to be able to run it there.
The easiest way to install a web server and PHP onto a windows computer is using either WAMP or XAMPP both of which install a complete package of web server languages and tools.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">





I'm testing on the Net. All other browsers, render fine. IE destroys the page, it's originally a PHP page but it's parsed. This is ridicules damn IE.

Visit The Blog | Follow On Twitter
301tool 1.1.5 - URL redirector & shortener (PHP/MySQL)
Can be hosted on and utilize your own domain





(link)

That looks more like a problem with the CSS where you are using hacks that several versions of IE recognise but which are only needed for one version of IE.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">





I need a condition for IE 7 +, owww.


Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





What about after IE 8 ?
Is there a list of conditions that I can check to analyze for IE7. I should probably remove the hacks I have in place.


IE9 doesn't have CCs, because they aren't needed. It's like other modern browsers. So good design shouldn't experience problems beyond 7 or 8.
Not sure exactly what you mean, but this syntax will only be read by IE7:Is there a list of conditions that I can check to analyze for IE7.
Code:* + html .whatever { styles here }
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





If that Syntax would only be read by IE7 and IE8,9 etc don't need anything then why is it breaking when I did have the *hack applied ?


There's plenty of other reasons why the page might be breaking. It doesn't look like PHP is being parsed on that page anyway, as it has a .htm extension. Normally, you'll need a .php extension, unless you've set up something via htaccess. But the PHP appear in the source code, so if you have, it's not working.
EDIT: O, maybe the htaccess is OK, but this at the top of your page isn't being parsed:
TryCode:<? session_start(); //This should always be near the top $logging = true; ?>
IE may not like that extra code above the doctype. Looks like your server is not supporting the shortand tag.Code:<?php session_start(); //This should always be near the top $logging = true; ?>
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





Didn't work![]()


Did you do it? Code is the same.
What's in your htaccess file?
EDIT: O, it has changed (maybe I needed to refresh), but the cosing tag has gone now.
Details, details ...Code:<?php session_start(); //This should always be near the top $logging = true; ?>
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





Updated. Same negative results.![]()


OK, so the contents of the htaccess file? PHP isn't being parsed in your .htm page.
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





How can't it be ? It is working for all the other browsers.
The line in bold recently added# RewriteEngine on
# RewriteRule ^(.*)\.htm$ $1.php [nc]
AddType application/x-httpd-php .php .html


No it isn't. I'm viewing this in Firefox. It just doesn't choke on the unparsed PHP above the doctype.
That doesn't work for you, because your page is .htm, not .html. So use this instead:AddType application/x-httpd-php .php .html
Code:AddType application/x-httpd-php .php .htm .html
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





That is fixed, the IE problem still is there.


The PHP still isn't being parsed (view source in any browser. You shouldn't be able to see the PHP code at the top of the page. Some browsers will choke if there's anything above the doctype.) Are you sure your server handles htaccess files? Is it running Apache?
Facebook | Google+ | Twitter | Web Design Tips | Free Contact Form
Try your hand at the new JavaScript Challenge!
If you don't like getting your feet stuck in a bog, avoid Twitter BootsTrap.





My server can handle htaccess files. As for running Apache, not sure. I'll update.




Make sure php uses the starting <?php and not just <? - some php.ini files have short tags disabled. (XML also uses <? so there is a legitimate reason for turning it off)
I'll do anything to avoid working on my own code
Are you using: if (isset($_POST['submit'])) ?
IE has a bug and does not always send the value.
To pinpoint the error, try changing the extension to .php. This will tell you whether it's your PHP installation or your .htaccess file that's the culprit.
Bookmarks