Ho riattivato il link..lo lascio attivo solo per oggi...
comunque gli errori sono qui...
Validation Output: 9 Errors
1. Warning Line 176, Column 201: cannot generate system identifier for general entity "task"
…it/index.php?option=com_chronocontact&task=send&chronoformname=libroantispam&I…
✉
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 176, Column 201: general entity "task" not defined and no default entity
…it/index.php?option=com_chronocontact&task=send&chronoformname=libroantispam&I…
✉
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 176, Column 205: reference not terminated by REFC delimiter
…ndex.php?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemi…
✉
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 176, Column 205: reference to external entity in attribute value
…ndex.php?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemi…
✉
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 176, Column 205: reference to entity "task" for which no system identifier could be generated
…ndex.php?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemi…
✉
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 176, Column 200: entity was defined here
….it/index.php?option=com_chronocontact&task=send&chronoformname=libroantispam&…
7. Warning Line 176, Column 211: cannot generate system identifier for general entity "chronoformname"
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" …
✉
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.
8. Error Line 176, Column 211: general entity "chronoformname" not defined and no default entity
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" …
✉
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.
9. Warning Line 176, Column 225: reference not terminated by REFC delimiter
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
10. Warning Line 176, Column 225: reference to external entity in attribute value
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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 '&'.
11. Error Line 176, Column 225: reference to entity "chronoformname" for which no system identifier could be generated
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
12. Info Line 176, Column 210: entity was defined here
…php?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35"…
13. Warning Line 176, Column 240: cannot generate system identifier for general entity "Itemid"
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
14. Error Line 176, Column 240: general entity "Itemid" not defined and no default entity
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
15. Warning Line 176, Column 246: reference not terminated by REFC delimiter
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
16. Warning Line 176, Column 246: reference to external entity in attribute value
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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 '&'.
17. Error Line 176, Column 246: reference to entity "Itemid" for which no system identifier could be generated
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
✉
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.
18. Info Line 176, Column 239: entity was defined here
…hp?option=com_chronocontact&task=send&chronoformname=libroantispam&Itemid=35" >
19. Error Line 176, Column 80: EntityRef: expecting ';'
…<form name="ChronoContact_libroantispam" id="ChronoContact_libroantispam" meth…
✉
20. Error Line 176, Column 80: EntityRef: expecting ';'
…<form name="ChronoContact_libroantispam" id="ChronoContact_libroantispam" meth…
✉
21. Error Line 176, Column 80: EntityRef: expecting ';'
…<form name="ChronoContact_libroantispam" id="ChronoContact_libroantispam" meth…
Io per oggi non provo la patch cosě potete eventualmente vedere gli errori...
poi domani la provo e vediamo che succede..
