Line 31, Column 7: required attribute "type" not specified
<style> 
✉
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>.
 
 Line 58, Column 7: required attribute "type" not specified
<style>
✉
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>.
 
 Line 58, Column 7: document type does not allow element "style" here
<style>
✉
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).
 
 Line 67, Column 161: cannot generate system identifier for general entity "ccm_token"
…cID=47&amp;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0cc
✉
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 "&amp;" (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 &aelig; 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 67, Column 161: general entity "ccm_token" not defined and no default entity
…cID=47&amp;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0cc
✉
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 67, Column 170: reference not terminated by REFC delimiter
…p;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0cc9f94b0c1b
✉
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 67, Column 170: reference to external entity in attribute value
…p;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0cc9f94b0c1b
✉
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 '&amp;'.
 
 Line 67, Column 170: reference to entity "ccm_token" for which no system identifier could be generated
…p;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0cc9f94b0c1b
✉
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 67, Column 159: entity was defined here
…p?cID=47&amp;bID=18&amp;arHandle=Main&ccm_token=1258082719:169ae9195c0d8805f0
 Line 67, Column 234: cannot generate system identifier for general entity "method"
…f0cc9f94b0c1bbc1&amp;btask=passthru&method=submit_form">
✉
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 "&amp;" (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 &aelig; 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 67, Column 234: general entity "method" not defined and no default entity
…f0cc9f94b0c1bbc1&amp;btask=passthru&method=submit_form">
✉
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 67, Column 240: reference not terminated by REFC delimiter
…94b0c1bbc1&amp;btask=passthru&method=submit_form">
✉
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 67, Column 240: reference to external entity in attribute value
…94b0c1bbc1&amp;btask=passthru&method=submit_form">
✉
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 '&amp;'.
 
 Line 67, Column 240: reference to entity "method" for which no system identifier could be generated
…94b0c1bbc1&amp;btask=passthru&method=submit_form">
✉
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 67, Column 232: entity was defined here
…05f0cc9f94b0c1bbc1&amp;btask=passthru&method=submit_form">
 Line 67, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…iSurveyView18" class="miniSurveyView" method="post" action="/concrete5/index.…
✉
 Line 67, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…iSurveyView18" class="miniSurveyView" method="post" action="/concrete5/index.…
✉