Thanks for the excellent script.
Just got one little query.
I'm trying hard to make my site W3.org valid, and it appears this script creates a few issues, here is the validation report.
Any idea if (and how...) this could be resolved?
Just got one little query.
I'm trying hard to make my site W3.org valid, and it appears this script creates a few issues, here is the validation report.
Any idea if (and how...) this could be resolved?
1. Warning Line 73 column 108: cannot generate system identifier for general entity "task".
...="index.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
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.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
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.
✉
2. Error Line 73 column 108: general entity "task" not defined and no default entity.
...="index.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&«») in an URL or body text. See the previous message for further details.
✉
3. Warning Line 73 column 112: reference not terminated by REFC delimiter.
...dex.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
✉
4. Warning Line 73 column 112: reference to external entity in attribute value.
...dex.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
✉
5. Error Line 73 column 112: reference to entity "task" for which no system identifier could be generated.
...dex.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&«») in an URL or body text. See the previous message for further details.
✉
6. Info Line 73 column 107: entity was defined here.
...n="index.php?option=com_chronocontact&task=send&chronoformname=Landlord" >
7. Warning Line 73 column 118: cannot generate system identifier for general entity "chronoformname".
...p?option=com_chronocontact&task=send&chronoformname=Landlord" >
✉
8. Error Line 73 column 118: general entity "chronoformname" not defined and no default entity.
...p?option=com_chronocontact&task=send&chronoformname=Landlord" >
✉
9. Warning Line 73 column 132: reference not terminated by REFC delimiter.
...hronocontact&task=send&chronoformname=Landlord" >
✉
10. Warning Line 73 column 132: reference to external entity in attribute value.
...hronocontact&task=send&chronoformname=Landlord" >
✉
11. Error Line 73 column 132: reference to entity "chronoformname" for which no system identifier could be generated.
...hronocontact&task=send&chronoformname=Landlord" >
✉
12. Info Line 73 column 117: entity was defined here.
...hp?option=com_chronocontact&task=send&chronoformname=Landlord" >