Views: 54
Inactive
Hi, I have no idea how to validate html errors and css errors,
By the way, If i use WordPress as a blog, How to validate WordPress?
Thanks for Any suggestions
Black Belt
I'm not exactly sure what the question is. You can go here: http://validator.w3.org/ and enter your site's URL to see a list of errors. Same with your Wordpress URL.
Inactive
stevesh:
I'm not exactly sure what the question is. You can go here: http://validator.w3.org/ and enter your site's URL to see a list of errors. Same with your Wordpress URL.
Thanks, stevesh
They tell how many errors i get,
But did not show me where or which file i can fix that error,
Do Zen Cart forum list any **tutorials **about how to do validation?
Black Belt
There's no tutorial I'm aware of. If we had a link to the site, we could take a look and possibly advise.
Inactive
stevesh:
There's no tutorial I'm aware of. If we had a link to the site, we could take a look and possibly advise.
Ok, the errors are posted as follow:
***Line 294, Column 13: end tag for "ul" which is not finished
</ul>
✉
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.***
Line 363, Column 85: general entity "inc_subcat" not defined and no default entity
….php?main_page=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">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 363, Column 95: reference to entity "inc_subcat" for which no system identifier could be generated
…page=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></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.
Line 363, Column 98: general entity "pfrom" not defined and no default entity
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 363, Column 103: reference to entity "pfrom" for which no system identifier could be generated
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 363, Column 106: general entity "pto" not defined and no default entity
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 363, Column 109: reference to entity "pto" for which no system identifier could be generated
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 363, Column 113: general entity "sort" not defined and no default entity
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 363, Column 117: reference to entity "sort" for which no system identifier could be generated
…age=advanced_search_result&inc_subcat=1&pfrom=0&pto=50&sort=3a">0 - 50</a></li>
✉
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 364, Column 95: reference to entity "inc_subcat" for which no system identifier could be generated
…page=advanced_search_result&inc_subcat=1&pfrom=50&pto=100&sort=3a">50 - 100</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.
Line 364, Column 103: reference to entity "pfrom" for which no system identifier could be generated
…advanced_search_result&inc_subcat=1&pfrom=50&pto=100&sort=3a">50 - 100</a></li>
✉
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 364, Column 110: reference to entity "pto" for which no system identifier could be generated
…advanced_search_result&inc_subcat=1&pfrom=50&pto=100&sort=3a">50 - 100</a></li>
✉
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 364, Column 119: reference to entity "sort" for which no system identifier could be generated
…advanced_search_result&inc_subcat=1&pfrom=50&pto=100&sort=3a">50 - 100</a></li>
✉
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 365, Column 95: reference to entity "inc_subcat" for which no system identifier could be generated
…page=advanced_search_result&inc_subcat=1&pfrom=100&pto=200&sort=3a">100 - 200<…
✉
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 365, Column 95: reference to entity "inc_subcat" for which no system identifier could be generated
…page=advanced_search_result&inc_subcat=1&pfrom=100&pto=200&sort=3a">100 - 200<…
✉
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 365, Column 103: reference to entity "pfrom" for which no system identifier could be generated
…vanced_search_result&inc_subcat=1&pfrom=100&pto=200&sort=3a">100 - 200</a></li>
✉
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 365, Column 111: reference to entity "pto" for which no system identifier could be generated
…vanced_search_result&inc_subcat=1&pfrom=100&pto=200&sort=3a">100 - 200</a></li>
✉
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 365, Column 120: reference to entity "sort" for which no system identifier could be generated
…vanced_search_result&inc_subcat=1&pfrom=100&pto=200&sort=3a">100 - 200</a></li>
✉
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 366, Column 95: reference to entity "inc_subcat" for which no system identifier could be generated
…page=advanced_search_result&inc_subcat=1&pfrom=200&pto=300&sort=3a">200 - 300<…
✉
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 366, Column 103: reference to entity "pfrom" for which no system identifier could be generated
…vanced_search_result&inc_subcat=1&pfrom=200&pto=300&sort=3a">200 - 300</a></li>
✉
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 366, Column 111: reference to entity "pto" for which no system identifier could be generated
…vanced_search_result&inc_subcat=1&pfrom=200&pto=300&sort=3a">200 - 300</a></li>
✉
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.***
These are a part of them, My domain for those errors : https://www.uniwarestore.com
Fields marked required must be completed.
Tell staff why this post should be reviewed.
Required for login, security, and core site functionality.
Help us understand how the site is used so we can improve it.
Used for promotion and personalized campaign measurement.