A goog first step is to rename the page with a .phps extension and display
it in the browser. The coloring of the text often gives you an idea where
PHP got turned off or something critical was commented out.
Miles Thompson
At 09:55 PM 1/27/2002 -0700, Ben Turner wrote:
Parse error: parse
I just thought of this good tip:
To show the highlighted php source without constanly renaming your scripts
you can add the the following to your httpd.conf :
Alias /src /your/document/root
LocationMatch /src/*
ForceType application/x-httpd-php-source
/LocationMatch
Now, for
SHOW US YOUR CODE
-Original Message-
From: Ben Turner [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 27, 2002 10:56 PM
To: [EMAIL PROTECTED]
Subject: [PHP] Got a problem I cant figure out
Parse error: parse error in /var/www/docs/tacklebox/404handler.php on line
47
I am receiving
typically this means a missing semi-colon or a control structure that
wasn't closed somewhere in the code... it won't tell you where, so you'll
just have to check and double-check all the lines of code
At 08:28 AM 1/28/2002 -0600, Rick Emery wrote:
SHOW US YOUR CODE
-Original
Very likely a missing closing brace somewhere in your program. Look for
unpaired {'s or ('s or ['s.
On Sun, 2002-01-27 at 20:55, Ben Turner wrote:
Parse error: parse error in /var/www/docs/tacklebox/404handler.php on line 47
I am receiving this error on my page but the problem is that line
That error is always a missing } somewhere...
:)
Alex.
- Original Message -
From: Ben Turner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 28, 2002 5:55 AM
Subject: [PHP] Got a problem I cant figure out
Parse error: parse error in
6 matches
Mail list logo
