Jump to content

jayson

Members
  • Posts

    634
  • Joined

  • Last visited

Everything posted by jayson

  1. I tried that, and this is what I get? The domain or IP you entered wasn't found in our list.
  2. Just download fireftp, so far I like, So far I have yet to FTP any files, but I like the easy use of the program
  3. hmmmm, I enjoy coreFTP, it has been the best that I have used in a long time
  4. Andy has it right, I have 2 computers, a laptop and desktop, the laptop has an ip address of XX.XX.XX.X0 and XX.XX.XX.X1 me and my wife play net games sitting acreoss from each other, so there is more going on.
  5. girls
  6. SMF has a new update SMF 1.1rc2, just installed, and did what I did before, and NO ERROR!!!! so this up date seems to work ok here is the link SMF update
  7. ok, mine says cpanel 10, and I have coppermine in mine, but I still say the best bet is to delete all files and start again, before I got mine running, it was 5 installs/uninstalls, and finally got it running
  8. what I would do, (and this is me) delete all the files, use your cpanel to install coppermine, it will save you lots of headaches, you seclect the top dir for the program to go into, and it does the rest, all then you will need to input is the db username db password. (TCH people, am I wrong in in what I just said?)
  9. well, so far the error has not come up, so I will see what happens when I shut down tonight and start it up in the morning
  10. if i am not mistaken, I think it would be http://********/dir name/admin (or install)/install.php been a long time for me
  11. just do not forget to change the permission from 777, or you will invite hackers glad you are figuring it out
  12. now I will probly get corrected here, you need to give the server 777 access so when you install the program, it can write to the proper directorys, ( I run coppermine myself) then after the program is installed, you want to change all the settings to either 665 or 755 I can never remember, I thing mine is set to 755 I really enjoy coppermine www.jaysarahandy.com/photos/index.php, hope that you got your answer here and will enjoy coppermine
  13. ok, I am now getting an error to do with FF, Cnat remember it all but it is something like: window register corrupt c:\window\register\prefix (not sure if that is right) \some numbers\firefox.exe is corrupt, pleaae run chkdsk utility to fix. what is causing this error, I will do a reboot and do a screen capture to be more percises ^^^^^^^^^^^^^^^^^^this is the error I get
  14. (bond) age
  15. spy
  16. it is the only program, ( that is free, that I know of) that will create frames in different styles, is there another such free program.?
  17. I also dislike FP, but love the way I can make frames without trying to code it by hand. I do not use it to build a website, just to make the frames ( I use cutehtml)
  18. Try this link, it has all mods for phpbb phpbb mods
  19. hmmmm, I am on server 112, why does that not show up in tchstatus?
  20. Ok, here is what IT says about my site, it was created using frontpage, so if it has errors, then that means that FP is no good: Below are the results of attempting to parse this document with an SGML parser. 1. Error Line 1 column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>". <html> The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid. ✉ 2. Error Line 7 column 6: end tag for element "HEAD" which is not open. </head> The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem. If this error occured in a script section of your document, you should probably read this FAQ entry. ✉ 3. Error Line 9 column 15: there is no attribute "ROWS". <frameset rows="0,*,43" bordercolor="lightblue" border="0" frameborder="0"> 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. ✉ 4. Error Line 9 column 36: there is no attribute "BORDERCOLOR". <frameset rows="0,*,43" bordercolor="lightblue" border="0" frameborder="0"> 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. ✉ 5. Error Line 9 column 55: there is no attribute "BORDER". <frameset rows="0,*,43" bordercolor="lightblue" border="0" frameborder="0"> 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. ✉ 6. Error Line 9 column 71: there is no attribute "FRAMEBORDER". ...ordercolor="lightblue" border="0" frameborder="0"> 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. ✉ 7. Error Line 9 column 74: element "FRAMESET" undefined. ...olor="lightblue" border="0" frameborder="0"> 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. ✉ 8. Error Line 10 column 14: there is no attribute "NAME". <frame name="top" scrolling="no" target="contents"> 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. ✉ 9. Error Line 10 column 30: there is no attribute "SCROLLING". <frame name="top" scrolling="no" target="contents"> 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. ✉ 10. Error Line 10 column 42: there is no attribute "TARGET". <frame name="top" scrolling="no" target="contents"> 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. ✉ 11. Error Line 10 column 52: element "FRAME" undefined. <frame name="top" scrolling="no" target="contents"> 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. ✉ 12. Error Line 11 column 17: there is no attribute "COLS". <frameset cols="155,*"border="0" bordercolor="lightblue"> 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. ✉ 13. Error Line 11 column 58: element "FRAMESET" undefined. <frameset cols="155,*"border="0" bordercolor="lightblue"> 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. ✉ 14. Error Line 12 column 45: there is no attribute "SRC". <frame name="contents" target="main" src="navbar.html"> 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. ✉ 15. Error Line 12 column 58: element "FRAME" undefined. <frame name="contents" target="main" src="navbar.html"> 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. ✉ 16. Error Line 13 column 40: element "FRAME" undefined. <frame name="main" src="2index.html"> 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. ✉ 17. Error Line 15 column 73: element "FRAME" undefined. ...ing="no" target="contents" src="footer.html"> 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. ✉ 18. Error Line 17 column 7: document type does not allow element "BODY" here. <body> 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).
  21. That validator is a joke, it is giving me errors, that are not errors. so for me if it is not broken, do not fix, if broken take hammer, hit twice (or more) and try again.
  22. Rob: can you explain how you get parties from tower?
  23. tower
  24. Mike, I can help you create the files if you want, it will take about 15 minutes, I do not need to go into your server, just need to know if you would like me to create the files for you. Jayson
  25. Mike <script type="text/javascript" src="layout.js"></script> <link rel="stylesheet" type="text/css" href="layout.css" /> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^just like it is above, you keep the link rel= for the .css the .js (javascript) there is no link rel= does this make sense? I do not want ot make more work for you. If your happy with the look, then stay with it.
×
×
  • Create New...