Ckforms 1.33 is not compatible with W3C standards

Questions and bug reports for current release of CKForms

Ckforms 1.33 is not compatible with W3C standards

Postby Teophile » Wed Oct 28, 2009 10:53 pm

Ckforms 1.33 is not compatible with W3C standards http://validator.w3.org/ :

↑ Top
Validation Output: 46 Errors

1. Error Line 91, Column 16: "DOCTYPE" declaration not allowed in instance

doctype: "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \"


2. Error Line 164, Column 27: character "\" not allowed in attribute specification list

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


3. Error Line 164, Column 27: document type does not allow element "hr" here

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {



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).
4. Error Line 164, Column 28: end tag for "hr" omitted, but OMITTAG NO was specified

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
5. Info Line 164, Column 23: start tag was here

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {

6. Error Line 168, Column 51: document type does not allow element "hr" here

jInsertEditorText('<hr id="system-readmore" />', editor);



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).
7. Error Line 628, Column 85: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

… font-weight: bold; color: #474a44;">Veuillez nous contacter par le formulair



The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
8. Error Line 636, Column 91: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

…"radio" value="Pertinent" checked />



"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" ...
9. Error Line 638, Column 44: ID "avis" already defined

…class="ckCSStop10 " name="avis" id="avis" type="radio" value="Intéressant" …



An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
10. Info Line 636, Column 43: ID "avis" first defined here

… class="ckCSStop10 " name="avis" id="avis" type="radio" value="Pertinent" che

11. Error Line 640, Column 44: ID "avis" already defined

…class="ckCSStop10 " name="avis" id="avis" type="radio" value="Manque des info



An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
12. Info Line 636, Column 43: ID "avis" first defined here

… class="ckCSStop10 " name="avis" id="avis" type="radio" value="Pertinent" che

13. Error Line 642, Column 44: ID "avis" already defined

…class="ckCSStop10 " name="avis" id="avis" type="radio" value="Sans intérêt"



An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
14. Info Line 636, Column 43: ID "avis" first defined here

… class="ckCSStop10 " name="avis" id="avis" type="radio" value="Pertinent" che

15. Error Line 644, Column 132: required attribute "alt" not specified

…re part de votre avis sur ce site" />



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>.
16. Error Line 645, Column 28: Attribute "htmlfor" is not a valid attribute

<div class="error" htmlfor="avis">



You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
17. Error Line 656, Column 104: required attribute "alt" not specified

…ng" title="Le nom est obligatoire" />



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>.
18. Error Line 668, Column 107: required attribute "alt" not specified

… title="Le prénom est obligatoire" />



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>.
19. Error Line 679, Column 113: required attribute "alt" not specified

…="Veuillez indiquer votre adresse" />



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>.
20. Error Line 684, Column 114: required attribute "alt" not specified

…"Veuillez indiquer votre localité" />



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>.
21. Error Line 689, Column 110: required attribute "alt" not specified

…tle="Veuillez indiquer votre pays" />



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>.
22. Error Line 695, Column 106: required attribute "alt" not specified

…" title="L'e-mail est obligatoire" />



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>.
23. Error Line 705, Column 108: required attribute "alt" not specified

…title="Le message est obligatoire" />



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>.
24. Error Line 728, Column 138: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

…la lettre d'information" checked />



"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" ...
25. Error Line 729, Column 153: required attribute "alt" not specified

…nscrire à la lettre d'information" />



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>.
26. Error Line 740, Column 133: required attribute "alt" not specified

…quer votre niveau de connaissance" />



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>.
27. Error Line 744, Column 136: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

…a3357da92fd49c2457" align="absmiddle"> &nbsp;



The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
28. Error Line 744, Column 137: required attribute "alt" not specified

…3357da92fd49c2457" align="absmiddle"> &nbsp;



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>.
29. Error Line 744, Column 138: end tag for "img" omitted, but OMITTAG NO was specified

…357da92fd49c2457" align="absmiddle"> &nbsp;



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
30. Info Line 744: start tag was here

p<img class="captchacode" src="/index.php?option=com_ckforms&amp;task=captcha&amp

31. Error Line 745, Column 124: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

…images/refresh.gif" align="absmiddle"> &nbsp;



The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
32. Error Line 745, Column 126: end tag for "img" omitted, but OMITTAG NO was specified

…ages/refresh.gif" align="absmiddle"> &nbsp;



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
33. Info Line 745: start tag was here

c<img alt="Refresh Captcha" class="captcharefresh" src="/components/com_ckforms/c

34. Error Line 748, Column 52: duplicate specification of attribute "class"

<div class="error" htmlfor="ck_captcha_code" class="error">



You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
35. Warning Line 722, Column 49: reference to non-existent ID "fichier"

<label class="ckCSSlabel " id="fichierlbl" for="fichier"> Joindre un fichier



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
36. Error Line 91, Column 14: XML Parsing Error: StartTag: invalid element name

doctype: "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \"


37. Error Line 164, Column 26: XML Parsing Error: error parsing attribute name

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


38. Error Line 164, Column 26: XML Parsing Error: attributes construct error

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


39. Error Line 164, Column 26: XML Parsing Error: Couldn't find end of Start Tag hr line 164

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


40. Error Line 630, Column > 80: XML Parsing Error: attributes construct error

…amp;view=ckforms&amp;task=send&amp;id=1" method="post" id="ckform" class="for…


41. Error Line 630, Column > 80: XML Parsing Error: Couldn't find end of Start Tag form line 630

…amp;view=ckforms&amp;task=send&amp;id=1" method="post" id="ckform" class="for…


42. Error Line 636, Column > 80: XML Parsing Error: Specification mandate value for attribute checked

…avis" type="radio" value="Pertinent" checked />…


43. Error Line 728, Column > 80: XML Parsing Error: Specification mandate value for attribute checked

…="lettre" type="checkbox" value="Je souhaite m'inscrire à la lettre d'informa…


44. Error Line 748, Column 58: XML Parsing Error: Attribute class redefined

<div class="error" htmlfor="ck_captcha_code" class="error">


45. Error Line 751, Column 6: XML Parsing Error: Opening and ending tag mismatch: img line 745 and div

</div>


46. Error Line 756, Column 7: XML Parsing Error: Opening and ending tag mismatch: img line 744 and form

</form>


47. Error Line 757, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 743 and td

</td></tr>


48. Error Line 757, Column 10: XML Parsing Error: Opening and ending tag mismatch: td line 627 and tr

</td></tr>


49. Error Line 758, Column 8: XML Parsing Error: Opening and ending tag mismatch: tr line 627 and table

</table>


50. Error Line 759, Column 6: XML Parsing Error: Opening and ending tag mismatch: table line 626 and div

</div>


51. Error Line 845, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 248 and body

</body>


52. Error Line 846, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 220 and html

</html>


53. Error Line 846, Column 7: XML Parsing Error: Premature end of data in tag html line 3

</html>


I can PM you the details of my test site.
Otherwise I passed through CKForm SARKI it is great except these problems with W3C compliance.

Tank You
Teophile
Teophile
 
Posts: 3
Joined: Wed Oct 28, 2009 10:45 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby snobbis » Thu Oct 29, 2009 8:40 am

What is SARKI ?
snobbis
 
Posts: 13
Joined: Mon Oct 26, 2009 8:36 am
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby pedrino » Thu Oct 29, 2009 9:32 am

Hi,

did you try the last release 1.3.3 b4 at :
http://cookex.eu/download/download.php

On your site there is javascript problem. Could you tell the HTML you use in your Joomla.

Regards

Pierre
User avatar
pedrino
Site Admin
 
Posts: 150
Joined: Tue Aug 25, 2009 1:13 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby Teophile » Fri Oct 30, 2009 11:06 am

Point 1: I reinstalled everything on my site with the latest versions and here are the errors http://validator.w3.org a form of tests I recontruit:
Validation Output: 7 Errors

1. Error Line 543, Column 107: required attribute "alt" not specified

… title="Merci de saisir votre nom" />



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>.
2. Error Line 544, Column 28: Attribute "htmlfor" is not a valid attribute

<div class="error" htmlfor="Nom">



You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
3. Error Line 555, Column 104: required attribute "alt" not specified

…ng" title="Saisissez votre prénom" />



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>.
4. Error Line 567, Column 95: required attribute "alt" not specified

…mg/info.png" title="Votre adresse" />



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>.
5. Error Line 579, Column 99: required attribute "alt" not specified

…nfo.png" title="Votre code postal" />



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>.
6. Error Line 590, Column 103: required attribute "alt" not specified

…png" title="Saisissez votre ville" />



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>.
7. Error Line 597, Column 102: required attribute "alt" not specified

….png" title="Votre adresse E_mail" />



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>.




Point 2 : I check required and when I submit I have no error message. Why?
Response: I found the cause, it is the plugin RokGZipper.
This plugiin compiles javascript and css then CKForms blocked.
http://www.rockettheme.com/extensions-joomla/rokgzipper

Tank you

Teophile
Teophile
 
Posts: 3
Joined: Wed Oct 28, 2009 10:45 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby bruxxjuhu » Sun Nov 01, 2009 1:37 pm

Hello!

I have a problem with CKForms 1.3.3.

All Sites are valid with W3C, but CKForms is causing 45 errors.
What is the matter for this and how can I solve this problems?

Code: Select all
Validation Output:  45 Errors

   1. Error Line 428, Column 125: document type does not allow element "link" here

      …ui.datepicker.css" 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).
   2. Error Line 429, Column 88: document type does not allow element "link" here

      …s/css/ckforms.css" 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).
   3. Warning Line 480, Column 70: cannot generate system identifier for general entity "task"

      …de').attr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
   4. Error Line 480, Column 70: general entity "task" not defined and no default entity

      …de').attr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
   5. Warning Line 480, Column 74: reference not terminated by REFC delimiter

      …r("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
   6. Error Line 480, Column 74: reference to entity "task" for which no system identifier could be generated

      …r("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
   7. Info Line 480, Column 68: entity was defined here

      …hacode').attr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

   8. Warning Line 480, Column 83: cannot generate system identifier for general entity "sid"

      …php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
   9. Error Line 480, Column 83: general entity "sid" not defined and no default entity

      …php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
  10. Warning Line 480, Column 86: reference not terminated by REFC delimiter

      …?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
  11. Error Line 480, Column 86: reference to entity "sid" for which no system identifier could be generated

      …?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉

      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.
  12. Info Line 480, Column 81: entity was defined here

      …x.php?option=com_ckforms&task=captcha&sid=" + Math.random());

  13. Warning Line 487, Column 44: cannot generate system identifier for general entity "view"

      …ction="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post

      ✉

      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.
  14. Error Line 487, Column 44: general entity "view" not defined and no default entity

      …ction="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post

      ✉

      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.
  15. Warning Line 487, Column 48: reference not terminated by REFC delimiter

      …n="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" id

      ✉

      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.
  16. Warning Line 487, Column 48: reference to external entity in attribute value

      …n="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" id

      ✉

      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;'.
  17. Error Line 487, Column 48: reference to entity "view" for which no system identifier could be generated

      …n="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" id

      ✉

      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.
  18. Info Line 487, Column 42: entity was defined here

      … action="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="po

  19. Warning Line 487, Column 61: reference not terminated by REFC delimiter

      …option=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" cla

      ✉

      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.
  20. Warning Line 487, Column 61: reference to external entity in attribute value

      …option=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" cla

      ✉

      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;'.
  21. Error Line 487, Column 61: reference to entity "task" for which no system identifier could be generated

      …option=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" cla

      ✉

      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.
  22. Info Line 480, Column 68: entity was defined here

      …hacode').attr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

  23. Warning Line 487, Column 67: cannot generate system identifier for general entity "id"

      …=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="fo

      ✉

      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.
  24. Error Line 487, Column 67: general entity "id" not defined and no default entity

      …=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="fo

      ✉

      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.
  25. Warning Line 487, Column 69: reference not terminated by REFC delimiter

      …om_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="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.
  26. Warning Line 487, Column 69: reference to external entity in attribute value

      …om_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="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;'.
  27. Error Line 487, Column 69: reference to entity "id" for which no system identifier could be generated

      …om_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="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.
  28. Info Line 487, Column 65: entity was defined here

      …on=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="

  29. Error Line 513, Column 28: Attribute "htmlfor" is not a valid attribute

      <div class="error" htmlfor="Betreff">

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  30. Error Line 596, Column 103: Attribute "wrap" is not a valid attribute. Did you mean "nowrap" or "accept-charset"?

      …="Nachricht" cols="" rows="10" wrap="default" ></textarea>

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  31. Warning Line 612, Column 65: reference not terminated by REFC delimiter

      …="/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c

      ✉

      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.
  32. Warning Line 612, Column 65: reference to external entity in attribute value

      …="/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c

      ✉

      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;'.
  33. Error Line 612, Column 65: reference to entity "task" for which no system identifier could be generated

      …="/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c

      ✉

      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.
  34. Info Line 480, Column 68: entity was defined here

      …hacode').attr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

  35. Warning Line 612, Column 77: reference not terminated by REFC delimiter

      …?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align=

      ✉

      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.
  36. Warning Line 612, Column 77: reference to external entity in attribute value

      …?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align=

      ✉

      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;'.
  37. Error Line 612, Column 77: reference to entity "sid" for which no system identifier could be generated

      …?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align=

      ✉

      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.
  38. Info Line 480, Column 81: entity was defined here

      …x.php?option=com_ckforms&task=captcha&sid=" + Math.random());

  39. Error Line 612, Column 128: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

      …a3357da92fd49c2457" align="absmiddle"> &nbsp;

      ✉

      The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
  40. Error Line 612, Column 129: required attribute "alt" not specified

      …3357da92fd49c2457" align="absmiddle"> &nbsp;

      ✉

      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>.
  41. Error Line 612, Column 130: end tag for "img" omitted, but OMITTAG NO was specified

      …357da92fd49c2457" align="absmiddle"> &nbsp;

      ✉

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
  42. Info Line 612: start tag was here

      c<img class="captchacode" src="/index.php?option=com_ckforms&task=captcha&sid=c4c

  43. Error Line 613, Column 124: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

      …images/refresh.gif" align="absmiddle"> &nbsp;

      ✉

      The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
  44. Error Line 613, Column 126: end tag for "img" omitted, but OMITTAG NO was specified

      …ages/refresh.gif" align="absmiddle"> &nbsp;

      ✉

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
  45. Info Line 613: start tag was here

      c<img alt="Refresh Captcha" class="captcharefresh" src="/components/com_ckforms/c

  46. Error Line 615, Column 157: required attribute "alt" not specified

      …e Zeichenfolge links im Bild ein." />

      ✉

      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>.
  47. Error Line 617, Column 52: duplicate specification of attribute "class"

      <div class="error" htmlfor="ck_captcha_code" class="error">

      ✉

      You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
  48. Warning Line 598, Column 54: reference to non-existent ID "Dateiupload1"

      <label class="ckCSSlabel " id="Dateiupload1lbl" for="Dateiupload1"> Dateiupload

      ✉

      This error can be triggered by:
          * A non-existent input, select or textarea element
          * A missing id attribute
          * A typographical error in the id attribute

      Try to check the spelling and case of the id you are referring to.
  49. Warning Line 602, Column 54: reference to non-existent ID "Dateiupload2"

      <label class="ckCSSlabel " id="Dateiupload2lbl" for="Dateiupload2"> Dateiupload

      ✉

      This error can be triggered by:
          * A non-existent input, select or textarea element
          * A missing id attribute
          * A typographical error in the id attribute

      Try to check the spelling and case of the id you are referring to.
  50. Warning Line 606, Column 54: reference to non-existent ID "Dateiupload3"

      <label class="ckCSSlabel " id="Dateiupload3lbl" for="Dateiupload3"> Dateiupload

      ✉

      This error can be triggered by:
          * A non-existent input, select or textarea element
          * A missing id attribute
          * A typographical error in the id attribute

      Try to check the spelling and case of the id you are referring to.
  51. Error Line 480, Column 73: XML Parsing Error: EntityRef: expecting ';'

      …ttr("src","index.php?option=com_ckforms&task=captcha&sid=" + Math.random());

      ✉
  52. Error Line 480, Column > 80: XML Parsing Error: EntityRef: expecting ';'

      …ex.php?option=com_ckforms&task=captcha&sid=" + Math.random());…

      ✉
  53. Error Line 487, Column 47: XML Parsing Error: EntityRef: expecting ';'

      …on="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" i

      ✉
  54. Error Line 487, Column 60: XML Parsing Error: EntityRef: expecting ';'

      …?option=com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" cl

      ✉
  55. Error Line 487, Column 68: XML Parsing Error: EntityRef: expecting ';'

      …com_ckforms&view=ckforms&task=send&id=1" method="post" id="ckform" class="for

      ✉
  56. Error Line 487, Column > 80: XML Parsing Error: attributes construct error

      …view=ckforms&task=send&id=1" method="post" id="ckform" class="form-validate c…

      ✉
  57. Error Line 487, Column > 80: XML Parsing Error: Couldn't find end of Start Tag form line 487

      …view=ckforms&task=send&id=1" method="post" id="ckform" class="form-validate c…

      ✉
  58. Error Line 612, Column 64: XML Parsing Error: EntityRef: expecting ';'

      …c="/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49

      ✉
  59. Error Line 612, Column 76: XML Parsing Error: EntityRef: expecting ';'

      …p?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align

      ✉
  60. Error Line 617, Column 58: XML Parsing Error: Attribute class redefined

      <div class="error" htmlfor="ck_captcha_code" class="error">

      ✉
  61. Error Line 620, Column 6: XML Parsing Error: Opening and ending tag mismatch: img line 613 and div

      </div>

      ✉
  62. Error Line 626, Column 7: XML Parsing Error: Opening and ending tag mismatch: img line 612 and form

      </form>

      ✉
  63. Error Line 627, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 611 and td

      </td></tr>

      ✉
  64. Error Line 627, Column 10: XML Parsing Error: Opening and ending tag mismatch: td line 485 and tr

      </td></tr>

      ✉
  65. Error Line 628, Column 8: XML Parsing Error: Opening and ending tag mismatch: tr line 485 and table

      </table>

      ✉
  66. Error Line 629, Column 6: XML Parsing Error: Opening and ending tag mismatch: table line 484 and div

      </div>

      ✉
  67. Error Line 631, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 428 and td

      </td>

      ✉
  68. Error Line 632, Column 5: XML Parsing Error: Opening and ending tag mismatch: td line 427 and tr

      </tr>

      ✉
  69. Error Line 634, Column 8: XML Parsing Error: Opening and ending tag mismatch: tr line 426 and table

      </table>

      ✉
  70. Error Line 635, Column 7: XML Parsing Error: Opening and ending tag mismatch: table line 422 and div

         </div>

      ✉
  71. Error Line 668, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 334 and body

      </body>

      ✉
  72. Error Line 669, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 133 and html

      </html>

      ✉
  73. Error Line 669, Column 7: XML Parsing Error: Premature end of data in tag html line 2

      </html>
bruxxjuhu
 
Posts: 2
Joined: Wed Sep 23, 2009 6:17 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby pedrino » Sun Nov 01, 2009 2:20 pm

Hi,

most of errors will be fixed in the next release.

Regards

Pierre
User avatar
pedrino
Site Admin
 
Posts: 150
Joined: Tue Aug 25, 2009 1:13 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby bruxxjuhu » Sun Nov 01, 2009 2:30 pm

Ok - thank you.
bruxxjuhu
 
Posts: 2
Joined: Wed Sep 23, 2009 6:17 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby Teophile » Mon May 03, 2010 8:02 pm

In the version 1.34Buid2 still full of error W3C :

Validation Output: 56 Errors

1. Error Line 70, Column 16: "DOCTYPE" declaration not allowed in instance

doctype: "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \…


2. Error Line 139, Column 27: character "\" not allowed in attribute specification list

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


3. Error Line 139, Column 27: document type does not allow element "hr" here

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {



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).
4. Error Line 139, Column 28: end tag for "hr" omitted, but OMITTAG NO was specified

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
5. Info Line 139, Column 24: start tag was here

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {

6. Error Line 143, Column 51: document type does not allow element "hr" here

jInsertEditorText('<hr id="system-readmore" />', editor);



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).
7. Error Line 440, Column 102: document type does not allow element "link" here

…href="/Tests_joomla_15x/components/com_ckforms/css/tips.css" 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).
8. Error Line 472, Column 42: document type does not allow element "br" here

…ail:'Please enter a valid email: <br /><span>E.g. yourname&#64;domain.com</spa…



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).
9. Error Line 472, Column 48: document type does not allow element "span" here

…:'Please enter a valid email: <br /><span>E.g. yourname&#64;domain.com</span>',



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).
10. Error Line 473, Column 38: document type does not allow element "br" here

url:'Please enter a valid url: <br /><span>E.g. http://www.domain.com</span>',



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).
11. Error Line 473, Column 44: document type does not allow element "span" here

url:'Please enter a valid url: <br /><span>E.g. http://www.domain.com</span>',



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).
12. Warning Line 486, Column 69: cannot generate system identifier for general entity "task"

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
13. Error Line 486, Column 69: general entity "task" not defined and no default entity

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
14. Warning Line 486, Column 73: reference not terminated by REFC delimiter

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
15. Error Line 486, Column 73: reference to entity "task" for which no system identifier could be generated

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
16. Info Line 486, Column 68: entity was defined here

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());

17. Warning Line 486, Column 82: cannot generate system identifier for general entity "sid"

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
18. Error Line 486, Column 82: general entity "sid" not defined and no default entity

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
19. Warning Line 486, Column 85: reference not terminated by REFC delimiter

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
20. Error Line 486, Column 85: reference to entity "sid" for which no system identifier could be generated

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());



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.
21. Info Line 486, Column 81: entity was defined here

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());

22. Error Line 504, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<p><div class="bloc_idee">Veuillez vous inscrire en remplissant tous les champs…



The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
23. Warning Line 506, Column 44: cannot generate system identifier for general entity "view"

… action="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="pos…



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.
24. Error Line 506, Column 44: general entity "view" not defined and no default entity

… action="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="pos…



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.
25. Warning Line 506, Column 48: reference not terminated by REFC delimiter

…ion="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" n…



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.
26. Warning Line 506, Column 48: reference to external entity in attribute value

…ion="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" n…



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;'.
27. Error Line 506, Column 48: reference to entity "view" for which no system identifier could be generated

…ion="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" n…



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.
28. Info Line 506, Column 43: entity was defined here

…m action="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="po…

29. Warning Line 506, Column 61: reference not terminated by REFC delimiter

…p?option=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" …



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.
30. Warning Line 506, Column 61: reference to external entity in attribute value

…p?option=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" …



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;'.
31. Error Line 506, Column 61: reference to entity "task" for which no system identifier could be generated

…p?option=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" …



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.
32. Info Line 486, Column 68: entity was defined here

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());

33. Warning Line 506, Column 67: cannot generate system identifier for general entity "id"

…on=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ck…



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.
34. Error Line 506, Column 67: general entity "id" not defined and no default entity

…on=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ck…



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.
35. Warning Line 506, Column 69: reference not terminated by REFC delimiter

…=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ckfo…



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.
36. Warning Line 506, Column 69: reference to external entity in attribute value

…=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ckfo…



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;'.
37. Error Line 506, Column 69: reference to entity "id" for which no system identifier could be generated

…=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ckfo…



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.
38. Info Line 506, Column 66: entity was defined here

…ion=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="c…

39. Warning Line 513, Column 116: reference not terminated by REFC delimiter

…" name="civilite" type="radio" value="Mademoiselle" />&nbsp;Mademoiselle&nbsp



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.
40. Warning Line 514, Column 104: reference not terminated by REFC delimiter

… ckCSStop10 " name="civilite" type="radio" value="Madame" />&nbsp;Madame&nbsp



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.
41. Warning Line 515, Column 108: reference not terminated by REFC delimiter

…SStop10 " name="civilite" type="radio" value="Monsieur" />&nbsp;Monsieur&nbsp



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.
42. Error Line 587, Column 151: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

…checkbox" value="Je souhaite m'inscrire à la lettre d'information" checked />



"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" ...
43. Warning Line 592, Column 99: reference not terminated by REFC delimiter

…_15x/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49…



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.
44. Warning Line 592, Column 99: reference to external entity in attribute value

…_15x/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49…



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;'.
45. Error Line 592, Column 99: reference to entity "task" for which no system identifier could be generated

…_15x/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49…



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.
46. Info Line 486, Column 68: entity was defined here

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());

47. Warning Line 592, Column 111: reference not terminated by REFC delimiter

…hp?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align…



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.
48. Warning Line 592, Column 111: reference to external entity in attribute value

…hp?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align…



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;'.
49. Error Line 592, Column 111: reference to entity "sid" for which no system identifier could be generated

…hp?option=com_ckforms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align…



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.
50. Info Line 486, Column 81: entity was defined here

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());

51. Error Line 592, Column 162: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

…ms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align="absmiddle"> &nbsp;



The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
52. Error Line 592, Column 163: required attribute "alt" not specified

…ms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align="absmiddle"> &nbsp;



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>.
53. Error Line 592, Column 164: end tag for "img" omitted, but OMITTAG NO was specified

…ms&task=captcha&sid=c4ce9d9bffcf8ba3357da92fd49c2457" align="absmiddle"> &nbsp;



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
54. Info Line 592, Column 1: start tag was here

<img id="captchacode" class="captchacode" src="/Tests_joomla_15x/index.php?opti…

55. Error Line 593, Column 141: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"

…5x/components/com_ckforms/captcha/images/refresh.gif" align="absmiddle"> &nbsp;



The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
56. Error Line 593, Column 143: end tag for "img" omitted, but OMITTAG NO was specified

…5x/components/com_ckforms/captcha/images/refresh.gif" align="absmiddle"> &nbsp;



You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
57. Info Line 593, Column 1: start tag was here

<img alt="Refresh Captcha" class="captcharefresh" src="/Tests_joomla_15x/compon…

58. Error Line 595, Column 161: required attribute "alt" not specified

…om_ckforms/img/info.png" title="Vous devez recopier les caractères affichés" />



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>.
59. Error Line 603, Column 29: ID "submit_bt" already defined

<input name="submit_bt" id="submit_bt" type="submit" value="Annuler" />



An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
60. Info Line 601, Column 29: ID "submit_bt" first defined here

<input name="submit_bt" id="submit_bt" type="submit" value="Envoyer" />

61. Warning Line 541, Column 45: reference to non-existent ID "pays"

<label class="ckCSSlabel" id="payslbl" for="pays"> Région / Pays



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
62. Warning Line 532, Column 48: reference to non-existent ID "adresse"

<label class="ckCSSlabel" id="adresselbl" for="adresse"> Adresse



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
63. Warning Line 517, Column 44: reference to non-existent ID "nom"

<label class="ckCSSlabel" id="nomlbl" for="nom"> Nom



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
64. Warning Line 537, Column 49: reference to non-existent ID "localite"

…abel class="ckCSSlabel" id="localitelbl" for="localite"> Code postal / Localité



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
65. Warning Line 511, Column 49: reference to non-existent ID "civilite"

<label class="ckCSSlabel" id="civilitelbl" for="civilite"> Civilité



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
66. Warning Line 545, Column 46: reference to non-existent ID "email"

<label class="ckCSSlabel" id="emaillbl" for="email"> E-mail



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
67. Warning Line 585, Column 62: reference to non-existent ID "lettre"

…lcklettre_titre " id="lettrelbl" for="lettre"> Inscription à la lettre d'infor…



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
68. Warning Line 525, Column 47: reference to non-existent ID "prenom"

<label class="ckCSSlabel" id="prenomlbl" for="prenom"> Prénom



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
69. Warning Line 581, Column 63: reference to non-existent ID "fichier"

…s="ckCSSlabelckfichier_titre" id="fichierlbl" for="fichier"> Joindre un fichier



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
70. Warning Line 554, Column 67: reference to non-existent ID "niveau"

…nnaissance_titre" id="niveaulbl" for="niveau"> Quel est votre connaissance de …



This error can be triggered by:
* A non-existent input, select or textarea element
* A missing id attribute
* A typographical error in the id attribute

Try to check the spelling and case of the id you are referring to.
71. Error Line 70, Column 14: StartTag: invalid element name

doctype: "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \…


72. Error Line 139, Column 26: error parsing attribute name

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


73. Error Line 139, Column 26: attributes construct error

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


74. Error Line 139, Column 26: Couldn't find end of Start Tag hr line 139

if (content.match(/<hr\s+id=("|')system-readmore("|')\s*\/*>/i)) {


75. Error Line 486, Column 72: EntityRef: expecting ';'

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());


76. Error Line 486, Column 80: EntityRef: expecting ';'

…perty('src', 'index.php?option=com_ckforms&task=captcha&sid=' + Math.random());


77. Error Line 506, Column 47: EntityRef: expecting ';'

…tion="index.php?option=com_ckforms&view=ckforms&task=send&id=1" method="post" …


78. Error Line 506, Column 60: EntityRef: expecting ';'

…hp?option=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform"…


79. Error Line 506, Column 68: EntityRef: expecting ';'

…n=com_ckforms&view=ckforms&task=send&id=1" method="post" name="ckform" id="ckf…


80. Error Line 513, Column 81: EntityRef: expecting ';'

…" name="civilite" type="radio" value="Mademoiselle" />&nbsp;Mademoiselle&nbsp


81. Error Line 514, Column 81: EntityRef: expecting ';'

… ckCSStop10 " name="civilite" type="radio" value="Madame" />&nbsp;Madame&nbsp


82. Error Line 515, Column 81: EntityRef: expecting ';'

…SStop10 " name="civilite" type="radio" value="Monsieur" />&nbsp;Monsieur&nbsp


83. Error Line 587, Column 80: Specification mandate value for attribute checked

…tre_champ" name="lettre" type="checkbox" value="Je souhaite m'inscrire à la le…


84. Error Line 592, Column 80: EntityRef: expecting ';'

… src="/Tests_joomla_15x/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9b…


85. Error Line 592, Column 80: EntityRef: expecting ';'

… src="/Tests_joomla_15x/index.php?option=com_ckforms&task=captcha&sid=c4ce9d9b…


86. Error Line 598, Column 6: Opening and ending tag mismatch: img line 593 and div

</div>


87. Error Line 606, Column 7: Opening and ending tag mismatch: img line 592 and form

</form>


88. Error Line 608, Column 5: Opening and ending tag mismatch: div line 591 and td

</td></tr>


89. Error Line 608, Column 10: Opening and ending tag mismatch: form line 506 and tr

</td></tr>


90. Error Line 609, Column 8: Opening and ending tag mismatch: td line 503 and table

</table>


91. Error Line 630, Column 8: Opening and ending tag mismatch: tr line 503 and div

</div></div></div></div></div></div></div></div></div></div>


92. Error Line 630, Column 14: Opening and ending tag mismatch: table line 502 and div

</div></div></div></div></div></div></div></div></div></div>


93. Error Line 659, Column 8: Opening and ending tag mismatch: div line 184 and body

</body>


94. Error Line 660, Column 7: Opening and ending tag mismatch: div line 184 and html

</html>


95. Error Line 660, Column 7: Premature end of data in tag body line 183

</html>


96. Error Line 660, Column 7: Premature end of data in tag html line 2

</html>




Super form manager but still young!

When will these changes be handled?

Thank you
Teophile
 
Posts: 3
Joined: Wed Oct 28, 2009 10:45 pm
Top

Re: Ckforms 1.33 is not compatible with W3C standards

Postby areasas » Tue Jun 29, 2010 6:36 pm

Very dears,

I am new to CKforms because I used other Extension which has no Data presentation capability. While, it was fully validated (having care to avoid the use of html text field!).

If you will solve the validation errors, as a counterpart, I will translate in Italian the user manual and I will also deeper check the Italian language file.

Let me know if it is good as a counterpart for your work and an approximate date so that I will send you the translation as much possible as BEFORE than your release. I will also send you the updated translation as I will go on, so that you will check that my position is reliable.

Just send me the confirmation and the approximate date and I will start.

Best wishes,

Carmine IACIOFANO
areasas
 
Posts: 1
Joined: Tue Jun 29, 2010 5:49 pm
Top


Return to CKForms 1.3.x Support forum

Who is online

Users browsing this forum: No registered users and 1 guest