Kewl, that fixed transparency issue, thanx. Can any of these 9 errors be fixed on your end?
Error Line 3, Column 8: duplicate specification of attribute “xmlns”
xmlns=”http://www.w3.org/1999/xhtml”
✉
You have specified an attribute more than once. Example: Using the “height” attribute twice on the same “img” tag.
Error Line 10, Column 107: end tag for “meta” omitted, but OMITTAG NO was specified
…nt=”width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=1″>
✉
You may have neglected to close an element, or perhaps you meant to “self-close” an element, that is, ending it with “/>” instead of “>”.
Info Line 10, Column 1: start tag was here
<meta name=”viewport” content=”width=device-width, initial-scale=1.0, maximum-s…
Warning Line 53, Column 110: cannot generate system identifier for general entity “subset”
…pis.com/css?family=Amaranth:700italic&subset=latin’ type=’text/css’ media=’all…
✉
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.
