Fw: [VE][338] New Error Message Suggestion

I found the answer, the .htaccess topok care of it.

The validator doesn't like the "&" in there since the correct format would be &

You can tell PHP to use & as the separator by using

ini_set("arg_separator.output","&");

at the beginning of your php file.
If you have access to your site's .htaccess files you can also put

php_value arg_separator.output &

in there. That will automatically set the arg_separator.output value for every page. Be careful though, you will need to configure the httpd.conf file with at least AllowOverride Options for this to work.

Kim

----- Original Message ----- 
From: Kim Steinhaug 
To: www-validator@w3.org 
Sent: Sunday, May 23, 2004 1:06 PM
Subject: [VE][338] New Error Message Suggestion


How can I avoid this error?

Below are the results of attempting to parse this document with an SGML parser. 

  1.. Line 36, column 161: cannot generate system identifier for general entity "PHPSESSID"

  ... - <a href="storefront.php?page=news&PHPSESSID=4454637f43504000ccc956c668d5c1

  An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

  Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

  Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 

  (Send feedback on message #338) 

Problem is that it is the PHP enginne which adds this &PHPSESSID into the code. How can I avoid this, since its really messing up the validation from really 0 errors to 250 occurencies of the above...

Mvh,
Kim Steinhaug
kim@steinhaug.com
www.steinhaug.com
 
_____________________________________
- - - - - -    Steinhaug Webutvikling  - - - - - - - -
- - - - - -  Hverdager 10.00 - 16.00 - - - - - - - -
 
Telefon : 88 00 92 45   -   Telefaks : 88 00 92 46
 
    Nettadresse : http://www.steinhaug.com/
     E-post adresse : firma@steinhaug.com
______________________________________