| m7sen |
12-08-2014 10:37 AM |
more
PHP Code:
Info Line 148, Column 170: entity was defined here
?b4arab.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&ut?
Warning Line 148, Column 208: cannot generate system identifier for general entity "utm_content"
?&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hre?
✉
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.
Error Line 148, Column 208: general entity "utm_content" not defined and no default entity
?&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hre?
✉
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.
Warning Line 148, Column 219: reference not terminated by REFC delimiter
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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.
Warning Line 148, Column 219: reference to external entity in attribute value
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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 '&'.
Error Line 148, Column 219: reference to entity "utm_content" for which no system identifier could be generated
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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.
Info Line 148, Column 207: entity was defined here
?s&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hr?
Warning Line 148, Column 313: reference not terminated by REFC delimiter
?ch.com/vbecommerce.php?productid=20&do=product&utm_source=xxxxxxx.com&utm_camp?
✉
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.
Warning Line 148, Column 313: reference to external entity in attribute value
?ch.com/vbecommerce.php?productid=20&do=product&utm_source=xxxxxxx.com&utm_camp?
✉
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 '&'.
Error Line 148, Column 313: reference to entity "do" for which no system identifier could be generated
?ch.com/vbecommerce.php?productid=20&do=product&utm_source=xxxxxxx.com&utm_camp?
✉
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.
Info Line 148, Column 108: entity was defined here
?h.com', '/vbecommerce.php?productid=20&do=product&utm_source=xxxxxxx.com&utm_c?
Warning Line 148, Column 332: reference not terminated by REFC delimiter
?php?productid=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks?
✉
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.
Warning Line 148, Column 332: reference to external entity in attribute value
?php?productid=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks?
✉
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 '&'.
Error Line 148, Column 332: reference to entity "utm_source" for which no system identifier could be generated
?php?productid=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks?
✉
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.
Info Line 148, Column 119: entity was defined here
?becommerce.php?productid=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Foo?
Warning Line 148, Column 357: reference not terminated by REFC delimiter
?ct&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Warning Line 148, Column 357: reference to external entity in attribute value
?ct&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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 '&'.
Error Line 148, Column 357: reference to entity "utm_campaign" for which no system identifier could be generated
?ct&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Info Line 148, Column 142: entity was defined here
?d=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=?
Warning Line 148, Column 383: reference not terminated by REFC delimiter
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Warning Line 148, Column 383: reference to external entity in attribute value
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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 '&'.
Error Line 148, Column 383: reference to entity "utm_medium" for which no system identifier could be generated
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Info Line 148, Column 170: entity was defined here
?b4arab.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&ut?
Warning Line 148, Column 421: reference not terminated by REFC delimiter
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">Advanced User Tag?
✉
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.
Warning Line 148, Column 421: reference to external entity in attribute value
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">Advanced User Tag?
✉
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 '&'.
Error Line 148, Column 421: reference to entity "utm_content" for which no system identifier could be generated
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">Advanced User Tag?
✉
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.
Info Line 148, Column 207: entity was defined here
?s&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hr?
Warning Line 149, Column 116: reference not terminated by REFC delimiter
?'/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Warning Line 149, Column 116: reference to external entity in attribute value
?'/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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 '&'.
Error Line 149, Column 116: reference to entity "utm_campaign" for which no system identifier could be generated
?'/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Info Line 148, Column 142: entity was defined here
?d=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=?
Warning Line 149, Column 142: reference not terminated by REFC delimiter
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Warning Line 149, Column 142: reference to external entity in attribute value
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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 '&'.
Error Line 149, Column 142: reference to entity "utm_medium" for which no system identifier could be generated
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Info Line 148, Column 170: entity was defined here
?b4arab.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&ut?
Warning Line 149, Column 180: reference not terminated by REFC delimiter
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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.
Warning Line 149, Column 180: reference to external entity in attribute value
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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 '&'.
Error Line 149, Column 180: reference to entity "utm_content" for which no system identifier could be generated
?=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" href="http://w?
✉
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.
Info Line 148, Column 207: entity was defined here
?s&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hr?
Warning Line 149, Column 279: reference not terminated by REFC delimiter
?m/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Warning Line 149, Column 279: reference to external entity in attribute value
?m/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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 '&'.
Error Line 149, Column 279: reference to entity "utm_campaign" for which no system identifier could be generated
?m/?utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUs?
✉
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.
Info Line 148, Column 142: entity was defined here
?d=20&do=product&utm_source=xxxxxxx.com&utm_campaign=Footer%2BLinks&utm_medium=?
Warning Line 149, Column 305: reference not terminated by REFC delimiter
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Warning Line 149, Column 305: reference to external entity in attribute value
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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 '&'.
Error Line 149, Column 305: reference to entity "utm_medium" for which no system identifier could be generated
?utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&utm_content=L?
✉
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.
Info Line 148, Column 170: entity was defined here
?b4arab.com&utm_campaign=Footer%2BLinks&utm_medium=Advanced%2BUser%2BTagging&ut?
Warning Line 149, Column 343: reference not terminated by REFC delimiter
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">vBulletin Mods &a?
✉
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.
Warning Line 149, Column 343: reference to external entity in attribute value
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">vBulletin Mods &a?
✉
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 '&'.
Error Line 149, Column 343: reference to entity "utm_content" for which no system identifier could be generated
?=Advanced%2BUser%2BTagging&utm_content=Lite" target="_blank">vBulletin Mods &a?
✉
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.
Info Line 148, Column 207: entity was defined here
?s&utm_medium=Advanced%2BUser%2BTagging&utm_content=Lite']);" rel="nofollow" hr?
|
More Information