Bumfuzzled again: PHP doesn't work on ONE (1) page <whimper /> ...

[barney]

I don't even know how to troubleshoot/research this one.  There's a local Apache/MySQL/PHP installation on my dev box, latest - I think? - versions of each.

PHP files load just fine from most of the subdirs of the Web root.  However, there's one HTML (index.html) file that simply does not allow PHP to be recognized.  It's driving me buggy.  I've tried reinstalling both Apache and PHP, to no avail.  Nothing I can find in the HTML and related CSS file(s) would appear to be normal.  But a simple

Code: PHP [Select]

1. <?php include 'file.ext'; ?>

doesn't work, nor does it highlight properly in the editor (Komodo Edit).  As stated in the post title, I'm bumfuzzled .

[Eóin]

One guess, shouldn't the extension have to be .php, i.e. index.php?

[mouser]

umm...

the lack of syntax highlighting should be a clue.

in php you need parentheses to use parentheses with include, as its a function.  e.g. include('file.ext'), don't you?
actually i see from php help pages you don't need parentheses.. though clearly your ide syntax highlighter thinks you do.. bah stupid language kludges.

[barney]

One guess, shouldn't the extension have to be .php, i.e. index.php?

-Eóin (March 22, 2011, 07:46 PM)

That lets PHP know it's a PHP page, but I've oft included

[Select]

<?php ... ?>

in html pages w/o harm.  Although, perhaps I need to make some adjustment to httpd.conf?

[Select]

<?php
    echo "Menu";
    include ('sidemenu.html');
  ?>

is the particular bit that's not being recognized.

Have I forgotten some httpd.conf configuration?  This is  a new installation, so I may have overlook some configuration, but I cannot see it (after many reviews of both httpd.conf and php.ini)

the lack of syntax highlighting should be a clue.

-mouser (March 22, 2011, 08:14 PM)

Yeah, I concur, but I cannot determine what the clue indicates.  Other pages indicate properly , some .html , some .php.

[barney]

 
I was calling the wrong file.
 

Doesn't change the rest of my confusion, though.

I was so certain of the file name that I never bothered to check that it was in place.  Damned dumb tyro error, ya know?

<sigh> Will I ever learn?</sigh>

[Boydon]

Next time just put a:

Code: PHP [Select]

1. <?php error_reporting(E_ALL | E_STRICT); ?>

at the beginning of you php file. This will enable very verbose warnings.

[barney]

[Select]

error_reporting = E_ALL & ~E_DEPRECATED

in PHP.ini ... but the error log being updated wasn't the error log I was tracking.  I seldom set PHP to report errors on-page, as that can significantly interfere with page structure.  I just lost track of which error log was being updated because of the multiple installs - basically, I confused myself  .

[widgewunner]

First thing to run/check is <?php phpinfo(); ?>

[barney]

First thing to run/check is <?php phpinfo(); ?>

-widgewunner (March 23, 2011, 09:13 PM)

Well ... yeah ... but running phpinfo(); doesn't correct for idiocy  .  'Sides, there are other issues that phpinfo(); won't correct <sigh /> .

[Renegade]

Not sure if this is relevant, but I came across a situation where <?php vs. <? vs. <?php[major version] broke with some of those being deprecated and made obsolete. It took me a while to figure out the problem. That was a while ago though, and I don't remember the specifics.

[barney]

Not sure if this is relevant, but I came across a situation where <?php vs. <? vs. <?php[major version] broke with some of those being deprecated and made obsolete. It took me a while to figure out the problem. That was a while ago though, and I don't remember the specifics.

-Renegade (March 23, 2011, 09:21 PM)

Oh, it is relevant ... fell into that trap many a time afore I disabled short keys.  Some servers just don't recognize 'em, and some servers want even more  .  Mostly a thing of the past, methinks, but definitely problematic at the time.