Even CSS-list spammers should have the sense to realise that their so-called "pro" solutions will be exposed for the amateurish rubbish that they really are if they insist on posting unsolicited links here :
SSC_perl wrote:> On Dec 4, 2013, at 8:03 PM, JAY TANNA wrote: > Frank > > Setting up shop has never been easier! > > http://www.somewhere/pro.php -------- > Notes and Potential Issues > > The following notes and warnings highlight missing or conflicting information > which caused the validator to perform some guesswork prior to validation, or > other things affecting the output below. If the guess or fallback is > incorrect, it could make validation results entirely incoherent. It is highly > recommended to check these potential issues, and, if necessary, fix them and > re-validate the document. > > Info Using Direct Input mode: UTF-8 character encoding assumed > > Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode > of the validator provides validated content in the form of characters pasted > or typed in the validator's form field. This will automatically make the data > UTF-8, and therefore the validator does not need to determine the character > encoding of your document, and will ignore any charset information specified. > > If you notice a discrepancy in detected character encoding between the > “Direct Input” mode and other validator modes, this is likely to be the > reason. It is neither a bug in the validator, nor in your document. > > ↑ Top > Validation Output: 8 Errors > > Error Line 9, Column 45: end tag for "meta" omitted, but OMITTAG NO was > specified > > <meta name="robots" content="index, follow"> > > ✉ > > 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 9, Column 1: start tag was here > > <meta name="robots" content="index, follow"> > > Error Line 49, Column 23: document type does not allow element "style" > here > > <style type="text/css"> > > ✉ > > The element named above was found in a context where it is not allowed. > This could mean that you have incorrectly nested elements -- such as a > "style" element in the "body" section instead of inside "head" -- or two > elements that overlap (which is not allowed). > > One common cause for this error is the use of XHTML syntax in HTML > documents. Due to HTML's rules of implicitly closed elements, this error can > create cascading effects. For instance, using XHTML's "self-closing" tags for > "meta" and "link" in the "head" section of a HTML document may cause the > parser to infer the end of the "head" section and the beginning of the "body" > section (where "link" and "meta" are not allowed; hence the reported error). > Warning Line 116, Column 55: cannot generate system identifier for > general entity "aff_id" > > …"http://ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130"; > target="_blank"… > > ✉ > > 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 116, Column 55: general entity "aff_id" not defined and no > default entity > > …"http://ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130"; > target="_blank"… > > ✉ > > 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 116, Column 61: reference not terminated by REFC delimiter > > …//ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" > target="_blank"><img … > > ✉ > > 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 116, Column 61: reference to external entity in attribute > value > > …//ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" > target="_blank"><img … > > ✉ > > 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 116, Column 61: reference to entity "aff_id" for which no > system identifier could be generated > > …//ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" > target="_blank"><img … > > ✉ > > 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 116, Column 54: entity was defined here > > …="http://ref.name.com/aff_c?offer_id=3&aff_id=6695&file_id=130"; > target="_blank… > > Warning Line 116, Column 67: cannot generate system identifier for > general entity "file_id" > > …name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="g… > > ✉ > > 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 116, Column 67: general entity "file_id" not defined and no > default entity > > …name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="g… > > ✉ > > 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 116, Column 74: reference not terminated by REFC delimiter > > …m/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="graphics… > > ✉ > > 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 116, Column 74: reference to external entity in attribute > value > > …m/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="graphics… > > ✉ > > 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 116, Column 74: reference to entity "file_id" for which no > system identifier could be generated > > …m/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="graphics… > > ✉ > > 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 116, Column 66: entity was defined here > > ….name.com/aff_c?offer_id=3&aff_id=6695&file_id=130" target="_blank"><img > src="… > > Error Line 116, Column 270: required attribute "alt" not specified > > …br /><img src="graphics/name-aff.png" width="468" height="60" border="0" > /></a> > > ✉ > > The attribute given above is required for an element that you've used, > but you have omitted it. For instance, in most HTML and XHTML document types > the "type" attribute is required on the "script" element and the "alt" > attribute is required for the "img" element. > > Typical values for type are type="text/css" for <style> and > type="text/javascript" for <script>. > Error Line 140, Column 35: the name and VI delimiter can be omitted from > an attribute specification only if SHORTTAG YES is specified > > <hr width="90%" size="3" noshade /> > > ✉ > > "VI delimiter" is a technical term for the equal sign. This error message > means that the name of an attribute and the equal sign cannot be omitted when > specifying an attribute. A common cause for this error message is the use of > "Attribute Minimization" in document types where it is not allowed, in XHTML > for instance. > > How to fix: For attributes such as compact, checked or selected, do not > write e.g <option selected ... but rather <option selected="selected" ... ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
