On Sep 27, 2013, at 12:52 PM, Sasa Rakic - Gmail wrote:
> Modern frameworks do not close php tag code:
>
> Could you please elaborate why modern frameworks are omitting ?>
I won't debate the statement why "modern frameworks are omitting ?>"
What I will say that is that I've been writing PHP
Hi Sasa
Thanks for your explanation.
Best regards,
Robert
From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On
Behalf Of Sasa Rakic - Gmail
Sent: Friday, September 27, 2013 7:00 PM
To: 'NYPHP Talk'
Subject: Re: [nyphp-talk] Help With My Contact Cent
: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On
Behalf Of Robert Stoll
Sent: Friday, September 27, 2013 6:56 PM
To: 'NYPHP Talk'
Subject: Re: [nyphp-talk] Help With My Contact Centre Website
Hi,
Could you please elaborate why modern frameworks are omitting ?&g
Help With My Contact Centre Website
Hi,
Modern frameworks do not close php tag
in modern frameworks it will be
mailto:talk-boun...@lists.nyphp.org] On
Behalf Of Jeff Slutz
Sent: Friday, September 27, 2013 6:46 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] Help With My Contact C
Hi,
Modern frameworks do not close php tag
in modern frameworks it will be
mailto:talk-boun...@lists.nyphp.org] On
Behalf Of Jeff Slutz
Sent: Friday, September 27, 2013 6:46 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] Help With My Contact Centre Website
I've also run int
I've also run into the "headers already sent" sort of issue being caused by
line breaks or white space after a closing php marker "?>". This is
considered output to the screen and then any following php header()
commands will fail.
--
Jeff Slutz
JSLEUTH LLC
2105 N Fork Drive
Lafayette, CO 80026
c
On Fri, Sep 27, 2013 at 10:04:53AM -0400, Tedd Sperling wrote:
> 1. The error "headers already sent " is created when you have already sent
> stuff to the browser and try to do it again. Functions that send/modify HTTP
> headers must be invoked before any output is made. Otherwise the call fails
Marvin:
I can't see the code, but I can tell a couple of things from the errors:
1. The error "headers already sent " is created when you have already sent
stuff to the browser and try to do it again. Functions that send/modify HTTP
headers must be invoked before any output is made. Otherwise t
