IE is Dumb can't parse PHP files

PHP
1

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

2

I can’t help with the problem, but yes, IE is dumb for a lot of reasons.

3

Browsers don’t parse PHP. It’s done on the server. Browsers just see the rendered HTML.

4

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 [URL=“http://www.apachefriends.org/en/xampp-windows.html”]XAMPP both of which install a complete package of web server languages and tools.

5

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.

6

Is it spitting out code on the page, or is it just issues with IE and HTML/CSS?

Do you have a link?

7

(link)

8

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.

9

I need a condition for IE 7 +, owww.

10 
<!--[if [COLOR="#FF0000"]gte[/COLOR] IE 7]><link rel="stylesheet" type="text/css" href="/css/ie.css"><![endif]-->

CCs only work up to IE8, though.

11

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.

12

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.

Is there a list of conditions that I can check to analyze for IE7.

Not sure exactly what you mean, but this syntax will only be read by IE7:

[COLOR="#FF0000"]* + html[/COLOR] .whatever {
  styles here
}
13

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 ?

14

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:

<?
session_start(); //This should always be near the top
$logging = true;
?>

Try

<?[COLOR="#FF0000"]php[/COLOR]
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.

15

Didn’t work :frowning:

16

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.

<?php
session_start(); //This should always be near the top
$logging = true;
[COLOR="#FF0000"]?>[/COLOR]

Details, details …

17

Updated. Same negative results. :frowning:

18

OK, so the contents of the htaccess file? PHP isn’t being parsed in your .htm page.

19

How can’t it be ? It is working for all the other browsers.

# RewriteEngine on

# RewriteRule ^(.*)\\.htm$ $1.php [nc]

AddType application/x-httpd-php .php .html

The line in bold recently added

20

No it isn’t. I’m viewing this in Firefox. It just doesn’t choke on the unparsed PHP above the doctype.

AddType application/x-httpd-php .php .html

That doesn’t work for you, because your page is .htm, not .html. So use this instead:

AddType application/x-httpd-php .php .htm .html