Gatsby,
Okay I design templates for blogger all my templates are based on the
minima template. your suggestion is not working because the code in
minima is filled with errors. these changes you have made have made it
impossible for me to do anything! My work is at a standstill. I tried
installing even templates that weren't made by me. I have gone to
every blog designer I know and all their templates give me BX errors-
too!
I did an experiment and copied the default minima code into W3C markup
validation service. the defalut minima coding had 25 in total.
So my question is- whos errors are you going to accept? your default
code has errors in it, by what standards are you basing this "fix" on.
I have alot of unhappy customers right now. so I am asking kindly,
whatever you did- Please fix this problem.
Thanks
Lena toews
http://www.simplyfabulousbloggertemplates.com/
Oh BTW here are your errors for the default Minima template:
Validation Output: 25 Errors
1. Error Line 3, Column 15: there is no attribute "expr:dir".
<html expr:dir='data:blog.languageDirection' xmlns='http://
www.w3.org/1999/xhtml
✉
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.
2. Error Line 5, Column 20: there is no attribute "data".
<b:include data='blog' name='all-head-content'/>
✉
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 5, Column 32: there is no attribute "name".
<b:include data='blog' name='all-head-content'/>
✉
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.
4. Error Line 5, Column 51: element "b:include" undefined.
<b:include data='blog' name='all-head-content'/>
✉
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).
5. Error Line 6, Column 32: element "data:blog.pageTitle"
undefined.
<title><data:blog.pageTitle/></title>
✉
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 7, Column 11: element "b:skin" undefined.
<b:skin><
|
