Jay Blanchard wrote:
[snip]
I might pull time zone rules and say that your 4:30 is my 5:30, and that
I'm already home. ;)
[/snip]
Another space-time continuum snafu brought to you by the Consortium For
Creative PHP Development
Remember the Prime Directive, Number One.
--
John C. Nichel
Üb
[snip]
I might pull time zone rules and say that your 4:30 is my 5:30, and that
I'm already home. ;)
[/snip]
Another space-time continuum snafu brought to you by the Consortium For
Creative PHP Development
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.ne
Jochem Maas wrote:
John Nichel wrote:
Bruce Gilbert wrote:
Your heredoc is messed up. Look into getting an editor which will
highlight the errors for you. This mailing list isn't here to syntax
check (unless it's 4:30 on a Friday).
can we hold you to that John ;-)
I might pull time z
yea, I was able to get the form to display, thanks.
On 8/11/05, Jay Blanchard <[EMAIL PROTECTED]> wrote:
> [snip]
> Your HEREDOC appears to be messed up. On line 623 the closing identifier
> is not in first column of the line (when I cut n paste the code into an
> editor. That is a requirement fo
[snip]
Your HEREDOC appears to be messed up. On line 623 the closing identifier
is not in first column of the line (when I cut n paste the code into an
editor. That is a requirement for the heredoc.
You also didn't close the PHP block after END_FORM;
Then you need to open a PHP block at about line
John Nichel wrote:
Bruce Gilbert wrote:
Your heredoc is messed up. Look into getting an editor which will
highlight the errors for you. This mailing list isn't here to syntax
check (unless it's 4:30 on a Friday).
can we hold you to that John ;-)
--
PHP General Mailing List (http://w
[snip]
Dude, when you have a syntax error like this only post 20 or 30 lines of
the code surrounding the line and then point out which line is #foo, 'k?
Your HEREDOC appears to be messed up. On line 623 the closing identifier
is not in first column of the line (when I cut n paste the code into an
[snip]
755 lines of code that should have never been posted in its entirity,
especially without line numbers or something saying <---HERE IS THE
PROBLEM LINE
[/snip]
Dude, when you have a syntax error like this only post 20 or 30 lines of
the code surrounding the line and then point out which line
Bruce Gilbert wrote:
Your heredoc is messed up. Look into getting an editor which will
highlight the errors for you. This mailing list isn't here to syntax
check (unless it's 4:30 on a Friday).
--
John C. Nichel
ÜberGeek
KegWorks.com
716.856.9675
[EMAIL PROTECTED]
--
PHP General Mailing
I don't see any missing semi-colons off hand. The error is supposedly
on line 556 in the below code:
Wealth Development Mortgage :: TEAM
HOME
CONTACT US
PAYMENT CALCULATOR
HOME
COMPANY
[snip]
I get this error a lot, and think it may be an easy fix, but don't
really know what to look for.
'Parse error: parse error, unexpected T_ENCAPSED_AND_WHITESPACE,
expecting T_STRING or T_VARIABLE or T_NUM_STRING in
/hsphere/local/home/bruceg/inspired-evolution.com/Contact_Form_Test.php
on li
11 matches
Mail list logo