Hi All,
I'm developing a website and one page is invalid according to the w3 Validator. It is a link to Multimap, to give directions to the company's office.
Validation Output: 9 Errors
Line 43, Column 53: cannot generate system identifier for general entity "countryCode"
…tp://www.multimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|…
✉
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.
Line 43, Column 53: general entity "countryCode" not defined and no default entity
…tp://www.multimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|…
✉
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.Line 43, Column 64: reference not terminated by REFC delimiter
…ltimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful…
✉
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.Line 43, Column 64: reference to external entity in attribute value
…ltimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful…
✉
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 '&'.Line 43, Column 64: reference to entity "countryCode" for which no system identifier could be generated
…ltimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful…
✉
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.Line 43, Column 52: entity was defined here
…ttp://www.multimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17…
Line 43, Column 95: cannot generate system identifier for general entity "bd"
…tryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0…
✉
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.
Line 43, Column 95: general entity "bd" not defined and no default entity
…tryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0…
✉
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.Line 43, Column 97: reference not terminated by REFC delimiter
…yCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.1…
✉
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.Line 43, Column 97: reference to external entity in attribute value
…yCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.1…
✉
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 '&'.Line 43, Column 97: reference to entity "bd" for which no system identifier could be generated
…yCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.1…
✉
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.Line 43, Column 94: entity was defined here
…ntryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-…
Line 43, Column 117: cannot generate system identifier for general entity "loc"
…6,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%…
✉
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.
Line 43, Column 117: general entity "loc" not defined and no default entity
…6,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%…
✉
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.Line 43, Column 120: reference not terminated by REFC delimiter
…0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%202…
✉
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.Line 43, Column 120: reference to external entity in attribute value
…0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%202…
✉
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 '&'.Line 43, Column 120: reference to entity "loc" for which no system identifier could be generated
…0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%202…
✉
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.Line 43, Column 116: entity was defined here
…06,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9…
Line 43, Column 63: EntityRef: expecting ';'
…ultimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=usefu…
✉
Line 43, Column 80: EntityRef: expecting ';'
…?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc…
✉
Line 43, Column 80: EntityRef: expecting ';'
…?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc…
Code:
<p><a href="http://www.multimap.com/maps/?qs=W9+2BE&countryCode=GB#map=51.52306,-0.19973|17|4&bd=useful_information&loc=GB:51.52302:-0.19974:16|W9%202BE|W9%202BE">Link to Map</a></p>Any ideas how to get that link to be valid?
Cheers,