NOT XHTML VALID ...

[pamelina]

Hello CMS Made Simple users ...

Just a quick question... Both (2) of my websites are XHTML valid.. but when I try to use {embed header=true} and {embed url=http://www.my_domain_name.com} IT FAILS to validate... Also when I try to use just {pi_iframe url="http://www.my_domain_name.com} IT FAILS TO VALIDATE ??!
The website within website works fine it just FAILS TO VALIDATE...
Is this a problem that can be solved in a future release of CMS Made Simple or is there an error on my side?

Looking forward to find out a solution...

[nils73]

Pamelina,

to help you solve your problem it would be useful to see the output. Otherwise it will be difficult to tell why the page does not validate. Maybe the validation error derives from including the head-section of your html-document twice ... which would be very simple to solve.

Regards,
Nils

[nuno]

Hello CMS Made Simple users ...

Just a quick question... Both (2) of my websites are XHTML valid.. but when I try to use {embed header=true} and {embed url=http://www.my_domain_name.com} IT FAILS to validate... Also when I try to use just {pi_iframe url="http://www.my_domain_name.com} IT FAILS TO VALIDATE ??!
The website within website works fine it just FAILS TO VALIDATE...
Is this a problem that can be solved in a future release of CMS Made Simple or is there an error on my side?

Looking forward to find out a solution...

If you embed for example google or another not validated site it NEVER validate,  you know that?
If you put my site embed  and YOUR site is validated i tell you all is correct!
If you provide to us more info for example your url we can try help you!

Nuno

[pamelina]

Nils73 and Nuno thank you for your quick reply ...

Here is the output of validation:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Validation Output:  16 Errors

   1. Error Line 146, Column 28: character ";" not allowed in attribute specification list.

      for (i=0; i" element),
          * by using vendor proprietary extensions such as "" or "" (this is usually fixed by using CSS to achieve the desired effect instead).
          * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
   3. Warning Line 150, Column 46: character "&" is the first character of a delimiter but occurred as data.

      if ((document.all || document.getElementById) && iframehide=="no"){

      ✉

      This message may appear in several cases:
          * You tried to include the "" instead of ">".
  12. Info Line 146, Column 11: start tag was here.

      for (i=0; i element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  14. Error Line 193, Column 140: there is no attribute "hspace".

      …0' frameborder='0' vspace='0' hspace='0' style='overflow:visible; height:395p

      ✉

      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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  15. Error Line 146, Column 28: XML Parsing Error: error parsing attribute name.

      for (i=0; i<iframeids.length; i++){

      ✉
  16. Error Line 146, Column 28: XML Parsing Error: attributes construct error.

      for (i=0; i<iframeids.length; i++){

      ✉
  17. Error Line 146, Column 28: XML Parsing Error: Couldn't find end of Start Tag iframeids.length line 146.

      for (i=0; i<iframeids.length; i++){

      ✉
  18. Error Line 150, Column 47: XML Parsing Error: xmlParseEntityRef: no name.

      if ((document.all || document.getElementById) && iframehide=="no"){

      ✉
  19. Error Line 150, Column 48: XML Parsing Error: xmlParseEntityRef: no name.

      if ((document.all || document.getElementById) && iframehide=="no"){

      ✉
  20. Error Line 159, Column 15: XML Parsing Error: xmlParseEntityRef: no name.

      if (currentfr && !window.opera){

      ✉
  21. Error Line 159, Column 16: XML Parsing Error: xmlParseEntityRef: no name.

      if (currentfr && !window.opera){

      ✉
  22. Error Line 161, Column 31: XML Parsing Error: xmlParseEntityRef: no name.

      if (currentfr.contentDocument && currentfr.contentDocument.body.offsetHeight) //

      ✉
  23. Error Line 161, Column 32: XML Parsing Error: xmlParseEntityRef: no name.

      if (currentfr.contentDocument && currentfr.contentDocument.body.offsetHeight) //

      ✉
  24. Error Line 163, Column 29: XML Parsing Error: xmlParseEntityRef: no name.

      else if (currentfr.Document && currentfr.Document.body.scrollHeight) //ie5+ syn…

      ✉
  25. Error Line 163, Column 30: XML Parsing Error: xmlParseEntityRef: no name.

      else if (currentfr.Document && currentfr.Document.body.scrollHeight) //ie5+ syn…

      ✉
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I believe it is somethig wrong with function.embed.php, when I use {embed} there are 16 errors, 8 warnings, but when I use {pi_iframe} there are about 5 errors .... Also when I try to fix it by removing ';'...&&... or adding just ',' it shows errors or it just stop functioning ...
When I use none of the above (embed or pi_iframe) it validates perfect ...
Is there any other solution with CMS Made Simple to put website within website with validation sucess ... ?

[nuno]

embed  plugin is cmsms core and is now fixed in svn (nothing much xhtml is validated is just a small js ignored stuff) , this means in 1.5 version is fixed , the pi_iframe is not the responsibility of team, however, this is not the right solution in this days


A site 100% validated mean  absolutely nothing, can be validated but improperly structured

Best Regards
Nuno Costa

Btw if you have provide in principle that information was much easier don't you think?

Thanks for that report

[pamelina]

I have downloaded it from SVN and replaced old embed plugin with new one and it still fails to validate as XHTML ... ??

[alby]

I have downloaded it from SVN and replaced old embed plugin with new one and it still fails to validate as XHTML ... ??

maybe is better if you provide a link of your site .....

Alby

[nuno]

I have downloaded it from SVN and replaced old embed plugin with new one and it still fails to validate as XHTML ... ??

pamelina this is a obsession or what? you don't pull from svn that is for sure  http://svn.cmsmadesimple.org/svn/cmsmad ... ches/1.2.x
how hard is fix that validation pamelina?


Nuno Costa


Just put "CDATA" stuff around of javascrpit ou pull from svn in that link above.

http://viewsvn.cmsmadesimple.org/filede ... .embed.php

[pamelina]

Hi Nuno,

Now it works ...  You're a great coder! I appreciate your devotion to the prloblem I had ...
CMSms is best ... Now that this problem was solved CMSms is the greatest ...
I'm sure it will get the first award next year ...
Thanks again for all the help ...

Pamelina