svenvideo.tk
Bagger, een 3
- Waarom je site in quirk-modus laden door characters voor je doc-type te zetten?
- .tk domein is bagger
- frameset voor je site, bagger
- Onlogisch opgebouwd. Waarom inloggen?
- Kijk eens naar je spelling en grammatica
- Site lijkt meer op een proeftuin dan dat het daadwerkelijk wat toevoegt aan waarde.
- Hoeveel inlogsystemen telt je site? En Als ik op [Uploaden] druk, zie ik tekst wegvallen.
- Waarom opeens een lelijke slecht vormgegeven Flash-formulier bij attracties?
Oh ja, je paint skillz zijn best matig....
Als je echte cartoons wilt tekenen, ga naar de boekhandel en koop: 'Striptekenen voor dummies'.
Gewijzigd op 26/05/2011 16:36:39 door - Ariën -
Mijn advies:
1) Bedenk goed wat je met je site wilt doen
2) Bedenk een goede layoutindeling
3) Maak de layout
4) Vullen maar
Gewijzigd op 26/05/2011 16:42:14 door - Ariën -
Daar leer je van ;-)
Anyway.. om je op weg te helpen:
http://www.pfz.nl/wiki/uploaden/
Mijn advies is om gewoon de site te herschrijven.
Je blogs bij de attracties, komen steeds bij hetzelfde uit. Of ik nu op de bal klik, of op het minatuurspoorweg, ik kom steeds op de Wereldhavendag uit.
Gewijzigd op 26/05/2011 16:45:04 door - Ariën -
Line 2, Column 1: 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.
Error Line 8, Column 18: there is no attribute "ROWS"
<frameset rows="*" framespacing="0" border="0" frameborder="NO">
?
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.
Error Line 8, Column 35: there is no attribute "FRAMESPACING"
<frameset rows="*" framespacing="0" border="0" frameborder="NO">
?
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.
Error Line 8, Column 46: there is no attribute "BORDER"
<frameset rows="*" framespacing="0" border="0" frameborder="NO">
?
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.
Error Line 8, Column 62: there is no attribute "FRAMEBORDER"
<frameset rows="*" framespacing="0" border="0" frameborder="NO">
?
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.
Error Line 8, Column 66: element "FRAMESET" undefined
<frameset rows="*" framespacing="0" border="0" frameborder="NO">
?
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).
Error Line 9, Column 16: there is no attribute "SRC"
<frame src="http://svenvideo.byethost6.com/" name="dot_tk_frame_content" sc…
?
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.
Error Line 9, Column 55: there is no attribute "NAME"
…http://svenvideo.byethost6.com/" name="dot_tk_frame_content" scrolling="auto" …
?
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.
Error Line 9, Column 88: there is no attribute "SCROLLING"
…venvideo.byethost6.com/" name="dot_tk_frame_content" scrolling="auto" noresize>
?
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.
Error Line 9, Column 103: "NORESIZE" is not a member of a group specified for any attribute
…venvideo.byethost6.com/" name="dot_tk_frame_content" scrolling="auto" noresize>
?
Error Line 9, Column 103: element "FRAME" undefined
…venvideo.byethost6.com/" name="dot_tk_frame_content" scrolling="auto" noresize>
?
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).
Error Line 12, Column 10: 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).
Beter stap je van een frameset af...
ga er geleik mee beginnen
ook niet echt een goede foutafhandeling:o
Dat klopt met alle frames en lelijke opmaak & scripting is dit niet echt een 'toevoeging' aan het web.
Gewijzigd op 26/05/2011 21:09:29 door Wesley PHP
Sven video op 26/05/2011 16:27:44:
Krijg alleen "Access denied for user 'xth_7502115'@'%' to database 'xth_7502115_svenvideo'" te zien.
En jij wilt weten wat ik daar van vind......?!
Gewijzigd op 26/05/2011 21:17:14 door Obelix Idefix
Obelix en Idefix op 26/05/2011 21:15:29:
Krijg alleen "Access denied for user 'xth_7502115'@'%' to database 'xth_7502115_svenvideo'" te zien.
En jij wilt weten wat ik daar van vind......?!
Sven video op 26/05/2011 16:27:44:
Krijg alleen "Access denied for user 'xth_7502115'@'%' to database 'xth_7502115_svenvideo'" te zien.
En jij wilt weten wat ik daar van vind......?!
Saracasme druipt er vanaf :P
Toevoeging op 26/05/2011 22:07:42:
Obelix en Idefix op 26/05/2011 21:15:29:
Krijg alleen "Access denied for user 'xth_7502115'@'%' to database 'xth_7502115_svenvideo'" te zien.
En jij wilt weten wat ik daar van vind......?!
Sven video op 26/05/2011 16:27:44:
Krijg alleen "Access denied for user 'xth_7502115'@'%' to database 'xth_7502115_svenvideo'" te zien.
En jij wilt weten wat ik daar van vind......?!
Saracasme druipt er vanaf :P
Vincent Huisman op 27/05/2011 10:07:30:
Wat een grap:
http://www.chrometheme.net/node/3584
http://www.chrometheme.net/node/3584
het werkt wel:P
Iedere theme werkt. Maar bij thema's gaat het om het uiterlijk. En dat is bij de jouwe wel een lachtertje. Neem dit op als commentaar waar je aan kan werken. Niet denken dat we je allemaal afzeiken ofzo. Maar blijf het steeds meer proberen en uiteindelijk kun je mooie thema's maken. Of websites. ;)