Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
See if you can get help from a CSS forum like http://csscreator.com
Thread Starter
Kyo
(@chssiadmin)
csscreator.com wasn’t much help at all.
Thread Starter
Kyo
(@chssiadmin)
Does any one know why its messing up the way it is?
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Have you tried validating it? It has 82 errors and that’s just the home page.
Even with those errors resolved, did you discuss with your boss whether the website was ever built for IE8?
Thread Starter
Kyo
(@chssiadmin)
I am currently working on those validation issues. The site was made back in 2011 or 2012 I believe. To him it doesn’t matter if it was built for it or not he would want it to work.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Yes, but the question of whether or not the website was built for IE8 is important because it leads on to how much work could be involved. Also has your boss seen whether the audience of the website is actually using IE8? It’s all well people saying “There are still people using IE8”, but that can be irrelevant if none of your audience actually use IE8.
A quick fix worth trying is to add respond.js as a conditional (lt IE9) to your theme. This fixes a lot of media query issues with IE8 and is certainly worth a try.
Thread Starter
Kyo
(@chssiadmin)
The person that would know if it was made for IE8 doesn’t work here any more and no one knows. So lets say its wasn’t made for it how much work would it take to get it to work with IE8? I’ve tried to tell him that not a whole lot of people use IE8 any more but he is always worried that what about those that are.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
That reminds me, you could also try an old IE “fixer” plugin http://wordpress.org/plugins/ie-css3-support/
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
If you find you have to manually fix someone’s crappy code, and it’s taking you a while, what I’ve found helps is step back a bit. I find once you know how much of your audience uses IE8 you can then work out how much time is reasonable/ feasible to spend fixing issues for those users. Then when you’ve consumed that allocated time you know it’s not actually worth it.
Thread Starter
Kyo
(@chssiadmin)
@andrew Nevins that plugin didn’t work.
Thread Starter
Kyo
(@chssiadmin)
@spankmarvin where could I find the responds.js at?
You can find it at https://github.com/scottjehl/Respond
Add it to your theme folder. From there you should hook into the wp_head hook to conditionally include the script (the following assumes you have placed respond.js in your_theme_folder/js/
function add_respond_ie() {
global $is_IE;
if ($is_IE) {
echo ('<!--[if lt IE 9]>
<script type="text/javascript" src="'.get_template_directory_uri().'/js/respond.js"></script>
<![endif]-->');
}
}
add_action('wp_head', 'add_respond_ie');
Have a go with that and see whether it makes a difference.
That theme, http://themble.com/bones/ is not supported here nor does the developer support it.
There is a forum that might be of help at https://github.com/eddiemachado/bones/issues
