![[HSX] HeadShot Xtreme is officially recognized by the Central Outpost as a genuine gaming organization.](https://www.headshotdomain.net/files/coRpSE/cnopseal_X74-MEW1.png "[HSX] HeadShot Xtreme is officially recognized by the Central Outpost as a genuine gaming organization.")
I am making this post in response to what is going on in
. I had to post the changes here, as the Evo site doesn't like me posting the edits. Something with the security setting on the site just doesn't allow me to post it.
I use HTML5 on my site where Evo comes with HTML4 active, but for those that want to have it HTML5, there are 2 files that will need to be edited. Very simple to do. If you want it, just do simple changes:
Open: public_html/header.php
Find:
and add a // in front of it, so it will look like this:
Under that, you will see that the next two lines have a // in front of them.
just remove both of those // on each line so it looks like:
Save & Close
The last edit you would need to do is in the
Open: public_html/includes/meta.php
Find: (On or around Line 67)
and add a // at the start of that.
Save & Close
Doing that should validate your site as HTML5, and if you were getting warnings on the self-closing tags, those should just switch to "info" warning you that if the attributes that precede the / aren't wrapped in quotes, it could cause issues.
For example:
Bad:
Good:
I hope that clarifies the confusing matter of the trailing forward slashes, (/). I know when I was first learning about it, it was confusing and many of the sites did not clarify it very well.
| Please login to see this link Get registered or Log in |
I use HTML5 on my site where Evo comes with HTML4 active, but for those that want to have it HTML5, there are 2 files that will need to be edited. Very simple to do. If you want it, just do simple changes:
Open: public_html/header.php
Find:
PHP: [ Select all ]
echo "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">
"; and add a // in front of it, so it will look like this:
PHP: [ Select all ]
//echo "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">
"; Under that, you will see that the next two lines have a // in front of them.
PHP: [ Select all ]
// echo '<!DOCTYPE html>';
// echo "<html lang=\""._LANGCODE."\" dir=\""._LANG_DIRECTION."\">
"; just remove both of those // on each line so it looks like:
PHP: [ Select all ]
echo '<!DOCTYPE html>';
echo "<html lang=\""._LANGCODE."\" dir=\""._LANG_DIRECTION."\">
"; Save & Close
The last edit you would need to do is in the
Open: public_html/includes/meta.php
Find: (On or around Line 67)
PHP: [ Select all ]
$metastring .= '<meta http-equiv="Content-Language" content="'._LANGCODE.'">'."
"; and add a // at the start of that.
PHP: [ Select all ]
//$metastring .= '<meta http-equiv="Content-Language" content="'._LANGCODE.'">'."
"; Save & Close
Doing that should validate your site as HTML5, and if you were getting warnings on the self-closing tags, those should just switch to "info" warning you that if the attributes that precede the / aren't wrapped in quotes, it could cause issues.
For example:
Bad:
Code: [ Select all ]
<img alt=Logo src=./logo.png/>Good:
Code: [ Select all ]
<img alt="Logo" src="./logo.png"/>I hope that clarifies the confusing matter of the trailing forward slashes, (/). I know when I was first learning about it, it was confusing and many of the sites did not clarify it very well.
Please be aware when doing this though, If the theme is not coded correctly, by this I mean, If the images have not had their sizes specified or their containers, the theme will not look right, You will see large gaps between image sets.
We will be changing the way theme are integrated in the near future, You will be able to specify the "doctype" directly from theme files, Like it should have been from the start.
We will be changing the way theme are integrated in the near future, You will be able to specify the "doctype" directly from theme files, Like it should have been from the start.
Is there any way of testing/checking to see if it is compliant after the edits?
Not really, You would just have to change the doctype, refresh the page and take a look, only real way to know for sure if edits are needed.
— Lonestar wroteNot really, You would just have to change the doctype, refresh the page and take a look, only real way to know for sure if edits are needed.
Okay, Everything seems fine right now. I'm just not sure what you mean by "change the doctype"
Thanks for the reply
coRpSE first message in this thread, shows you how to change the doctype of your site.
Last edited by Lonestar on Sat May 20, 2023 2:30 am; edited 1 time in total
— Lonestar wrotecoRpSE fiest message in this thread, shows you how to change the doctype of you site.
Yes, I saw that and did all the changes. I misunderstood and thought there was another setting I had to do.
Thanks for all the information and replies.
— UTBaDaSS wrote— Lonestar wrotecoRpSE fiest message in this thread, shows you how to change the doctype of you site.
Yes, I saw that and did all the changes. I misunderstood and thought there was another setting I had to do.
Thanks for all the information and replies. Â
This is for your site setting only for doctype as Lonestar and CoRpSE indicated. Any theme(s) being used (as Lonestar said) will have to be made in compliance with HTML 5, or you will see the error(s) in some shape or form. (IE: large gaps between image sets)
