The phpwcms support forum will help to find answers to your questions. The small but strong community is here since more than 10 years.
https://forum.phpwcms.org/
Code: Select all
Line 25, column 56: cannot generate system identifier for general entity "hashID"
...ve"><a href="index.php?o_que_fazemos&hashID=cd09858c574d79b31d33b9484b36861c"
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 "&" (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 æ 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.
Code: Select all
<ul>
<li><a href="index.php?id=1,0,0,1,0,0">About</a></li>
<li class="listActive"><a href="index.php?id=2,0,0,1,0,0">Portfolio</a></li>
</ul>
Code: Select all
Line 27, column 44: cannot generate system identifier for general entity "hashID"
...li><a href="index.php?id=1,0,0,1,0,0&hashID=3a7356815cfe9b8dfe97b55aa8950a84"
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 "&" (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 æ 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.
spirelli wrote:Sometimes something like "hashID=0cf69aba48af0a61&8203;505d4e9ce2b1aaed" gets added to the URL. This disturbs my site statistics as 0.125.0.0.1.0.phtml is counted as a different page than 0.125.0.0.1.0.phtml?hashID=0cf69aba48af0a61505d4e9ce2b1aaed although it is the same page. Would be nice id this 'attachment' would disappear with th next version.ogeorgi wrote: it's the neccessary Session ID. Not possible.
Oliver
Code: Select all
php_flag session.use_trans_sid off
Found it here:
ini_set( 'arg_separator.output' , '&' );
ini_set( 'url_rewriter.tags' , 'a=href,area=href,frame=src,input=src,fieldset=' );
the first part will make the automatic URL rewriting for sessions use the HTML entity & rather than the default &, which is invalid XHTML. the next line will add the hidden form input (which is valid XHTML) inside a <fieldset> rather than the default, immediately after the <form> tag, which is invalid XHTML. if you don't already have them, you need to put <fieldset> tags inside all <form> tags to get forms to work with PHP sessions. this will change the appearance of your forms, but you can change it back with some CSS styling.