481
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:53

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


the patch is for XOOPS 2.3.0

anything available for 2.0.17 or even 2.0.16.
and also shouldn,t these templates been modified in the 2.0.17 release.



482
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:48

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


so if the modules are not w3c compliant, any way to work around it.



483
nmshah
Re: how to make xoops w3c compliant
  • 2007/9/7 17:22

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


i m on 2.0.17
my default module is mastop publish, can this be the reason for errors

edited
my site url is http://makingdestiny.com

i have set default module as none. Rechecked with the validator, it still says 14 errors, these are:

Validation Output: 14 Errors

1. Error Line 46, Column 48: document type does not allow element "style" here.

<div class="blockContent"><style type="text/css">



The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
2. Error Line 127, Column 38: character ";" not allowed in attribute specification list.

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


3. Error Line 127, Column 38: element "menuids7743.length" undefined.

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



You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (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).
4. Error Line 129, Column 37: character ";" not allowed in attribute specification list.

for (var t=0; t<ultags.length; t++){


5. Error Line 129, Column 37: element "ultags.length" undefined.

for (var t=0; t<ultags.length; t++){



You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (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).
6. Error Line 169, Column 8: end tag for "ultags.length" omitted, but OMITTAG NO was specified.

</script>



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

for (var t=0; t<ultags.length; t++){

8. Error Line 169, Column 8: end tag for "menuids7743.length" omitted, but OMITTAG NO was specified.

</script>



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

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

10. Warning Line 182, Column 154: character "&" is the first character of a delimiter but occurred as data.

…ips' >Health, Goals, Honesty, People & Relationships</a></li>



This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "<"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.
11. Error Line 127, Column 38: XML Parsing Error: error parsing attribute name.

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


12. Error Line 127, Column 38: XML Parsing Error: attributes construct error.

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


13. Error Line 127, Column 38: XML Parsing Error: Couldn't find end of Start Tag menuids7743.length line 127.

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


14. Error Line 129, Column 37: XML Parsing Error: error parsing attribute name.

for (var t=0; t<ultags.length; t++){


15. Error Line 129, Column 37: XML Parsing Error: attributes construct error.

for (var t=0; t<ultags.length; t++){


16. Error Line 129, Column 37: XML Parsing Error: Couldn't find end of Start Tag ultags.length line 129.

for (var t=0; t<ultags.length; t++){


17. Error Line 182, Column > 80: XML Parsing Error: xmlParseEntityRef: no name.

…es/mastop_publish/?tac=Health%2C_Goals%2C_Honesty%2C_People_%26_Relationships…



484
nmshah
how to make xoops w3c compliant
  • 2007/9/7 16:42

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


i just tried the w3c validator on my site. i was using the default theme. It showed some 39 error.



485
nmshah
Re: using external scripts(phpld) with xoops
  • 2007/7/29 10:49

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


thank you for the reply, but i have already tried using weblink 1.44 but its missing a lot of key features that a link directory requires. For example the back link verification, sponsored listing, reciprocal verification at the time of listing etc. Is there some other XOOPS module that i can use. Or any ways of extending the features of weblink.



486
nmshah
using external scripts(phpld) with xoops
  • 2007/7/24 22:52

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


I want to make a link directory using phpld and use it with xoops. Is there anyway to do it. Say for example as a module or something. please help



487
nmshah
Problem with captcha module
  • 2007/7/2 11:07

  • nmshah

  • Just can't stay away

  • Posts: 556

  • Since: 2007/7/2 8


on installing the captcha module captcha image is not shown. the image debug info is

"Fatal error: Call to undefined function: imagettftext() in /home/nmshah/public_html/modules/captcha/class/captcha_x/class.captcha_x.php on line 294"

What am i doing wrong. Please help me

Apache version 1.3.37 (Unix)
PHP version 4.4.6
MySQL version 4.1.22-standard
Architecture i686
Operating system Linux




TopTop
« 1 ... 46 47 48 (49)



Login

Who's Online

68 user(s) are online (39 user(s) are browsing Support Forums)


Members: 0


Guests: 68


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits