[PHP] session_star() problem
Ok I am starting on small web site and using PHP 4 on Apache with FreeBSD 4.4 as the OS. I need to use sessions to pass some info around between pages but when I use session_start() I get the error msg below. Warning: Cannot send session cookie - headers already sent by (output started at /usr/home/gate/public_html/product_list.php:8) in /usr/home/gate/public_html/product_list.php on line 9 Warning: Cannot send session cache limiter - headers already sent (output started at /usr/home/gate/public_html/product_list.php:8) in /usr/home/gate/public_html/product_list.php on line 9 I get this msg if it is the only thing in the php script as well as if it is in an actually script that I am using. Maybe I don't php set up right or something else.Could some one please put me in the right direction. Greg please reply to my email as well as the newsgroup -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP] htmlentities is incomplete: does not cover rsquo etc
The string function htmlentities seems to have very incomplete coverage of the HTML entities listed in the HTML 4 spec. For example, it does not know about rsquo, lsquo, rdquo, ldquo, etc. This is confirmed by looking at the output of get_html_translation_table, which does not list these entities. My impression is that it covers those HTML entities that are in ISO-8859-1, but not the others. Is this deliberate? If so, the Manual is misleading because it suggests that all HTML entities are covered. Otherwise, is this a bug? Eddie -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] htmlentities is incomplete: does not cover rsquo etc
Thanks Jan, it's much clearer now. My knowledge about character encodings has multiplied 100-fold in the last 24 hours' research. Would it be a good idea for the PHP Manual to address some of these issues, by explaining good practice in encoding arbitrary user input in forms (for example), for the benefit of those, like me, for whom character sets are a bit of a black art? Also I still cannot persuade get_html_translation_table to list those non-Latin1 entities. This is not an important issue, since it appears to be only an information function, but it would be nice if it were consistent with htmlentities and html_entity_decode. Eddie From Jan G.B. 13/03/2009 17:27: 2009/3/13 Heddon's Gate Hotel : The string function htmlentities seems to have very incomplete coverage of the HTML entities listed in the HTML 4 spec. For example, it does not know about rsquo, lsquo, rdquo, ldquo, etc. This is confirmed by looking at the output of get_html_translation_table, which does not list these entities. My impression is that it covers those HTML entities that are in ISO-8859-1, but not the others. Is this deliberate? If so, the Manual is misleading because it suggests that all HTML entities are covered. Otherwise, is this a bug? Well, If you specify the input charset you'll have no problem at all. ;) >µ»n“¢µ€jæ', ENT_QUOTES, 'UTF-8'); ?> Latin1 AKA ISO-8859-1 doesn't have ldquo nor bdquo nor ndash and alike. Regards, -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
