Common DOCTYPE Declarations
HTML 5
<!DOCTYPE html>
HTML 4.01 Strict
This DTD contains all HTML elements and attributes, but does NOT INCLUDE presentational or deprecated elements (like font). Framesets are not allowed.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
HTML 4.01 Transitional
This DTD contains all HTML elements and attributes, INCLUDING presentational and deprecated elements (like font). Framesets are not allowed.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
HTML 4.01 Frameset
This DTD is equal to HTML 4.01 Transitional, but allows the use of frameset content.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
XHTML 1.0 Strict
This DTD contains all HTML elements and attributes, but does NOT INCLUDE presentational or deprecated elements (like font). Framesets are not allowed. The markup must also be written as well-formed XML.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
XHTML 1.0 Transitional
This DTD contains all HTML elements and attributes, INCLUDING presentational and deprecated elements (like font). Framesets are not allowed. The markup must also be written as well-formed XML.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
XHTML 1.0 Frameset
This DTD is equal to XHTML 1.0 Transitional, but allows the use of frameset content.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
XHTML 1.1
This DTD is equal to XHTML 1.0 Strict, but allows you to add modules (for example to provide ruby support for East-Asian languages).
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
I guess i assume all borwsers these days are using html5
so for me html5 is good enough
therefore <!DOCTYPE html> In HTML5 there is only one DOCTYPE declaration
you are talking about html 4, I'm not.
also
<script> in html5 without type is sufficient
you don't need
`<script type="text/javascript">`
The type attribute gives the language of the script or format of the data. If the attribute is present, its value must be a valid MIME type. The charset parameter must not be specified. The default, which is used if the attribute is absent, is "text/javascript".
If you are updating from non 2.1 theme with lot of view overrides, you really need to recreate these views in 2.1. You could cause all sort of issues otherwise. Just a cursory look there is already mark-up issues, it is worth validating, to catch thing like unclosed tags.
Comments
I recall this happening to other people using bootstrap , it turned out to be a Js problem but will need to search for the discussion
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
I installed you theme zip file.
and the user box pops up without a white space or line in popup in firefox and google and appears normally.
you might turn off all caching and minimizers and delete the .ini files in your cache folder.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Did you follow the upgrade instructions EVERY step here.
including
http://vanillaforums.org/discussion/26685/vanilla-2-1-stable-released/p1
Delete the files
/themes/mobile/views/discussions/helper_functions.php AND
/applications/dashboard/views/default.master.php
do you have the same issue with the bittersweet theme?
you also say you are using vanilla 2.1, I would upgrade to vanilla 2.1.1
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
This may be another unicode problem ?
http://vanillaforums.org/discussion/comment/212275/#Comment_212275
What editor do you use for the tpl ?
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
I am using notepad++ and yes, I followed the instruccions and deleted the files.
With the bitterseet theme there's no problem.
With the grayscale blue there's no problem in IE10, but the problem persist in Chrome, Firefox and earlier versions of IE.
In Firefox and IE all the things should go in the head (css, js...) are rendered inside the head, in Chrome they are rendered in the body.
@Peregrine, which browser did you use?
I will update to 2.1.1 tomorrow and see whats happens.
Thanks a lot guys.
firefox v31
chromium version 36
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
I would rewrite the default.master.php, try this
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
In HTML5 there is only one DOCTYPE declaration, and it is very simple:
<!DOCTYPE html>
http://www.w3schools.com/html/html5_intro.asp
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
yes but his master is a php according to that theme ... so it strict/transitional
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
Here is all the types and what they do
http://www.w3schools.com/tags/tag_doctype.asp
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
I guess i assume all borwsers these days are using html5
so for me html5 is good enough
therefore <!DOCTYPE html> In HTML5 there is only one DOCTYPE declaration
you are talking about html 4, I'm not.
also
The type attribute gives the language of the script or format of the data. If the attribute is present, its value must be a valid MIME type. The charset parameter must not be specified. The default, which is used if the attribute is absent, is "text/javascript".
http://www.w3.org/TR/html5-diff/
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Yes it does simplify things and the Vanilla default master is an html5 doc.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌
a bit of a mish-mash different Doctypes through out the vanilla source some html5 some html 4.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
I think this a bit of red hearing guys. The problem is malformed mark-up not doctypes.
Back on topic @DarkShared does the theme have a themehook file? Can you post that, and the default master.
grep is your friend.
just commenting on improvements along the way.
x00 here's the zip
http://vanillaforums.org/discussion/comment/214449/#Comment_214449
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
I make the discussion difficult to follow, and can be confusing as are shotgun debugging suggestions.
@DarkShared is there are reason why you need all those view overrides?
grep is your friend.
x00 I agree with you, we went off-topic.
99.99% of the time, i agree with you. This is the other .01% As far as the shotgunning, I commented on vri's proposed code.
here was his response, when I asked him essentially the same questions.
http://vanillaforums.org/discussion/comment/214454/#Comment_214454
http://vanillaforums.org/discussion/comment/214457/#Comment_214457
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Sorry that wasn’t meant to be accusatory.
grep is your friend.
If you are updating from non 2.1 theme with lot of view overrides, you really need to recreate these views in 2.1. You could cause all sort of issues otherwise. Just a cursory look there is already mark-up issues, it is worth validating, to catch thing like unclosed tags.
grep is your friend.
Also the edit user popup you would expect to be in the standard dashboard theme, the style you have shown in he pic doesn't match that.
grep is your friend.