v1.6.2 - Internet Explorer not displaying correctly

Was it a fresh install? You may just need to clear your cache

fresh install on server. And both IE on the server plus on two different workstations all doing the same thing.

Make sure ie isn't going in to compatibility mode. It's very likely to if
you're using a short name for your cms (ie http://servername as opposed to
http://servername.domain.com)

I tried with fqdn as suggested and also watched and toggled compatibility mode but it didn't appear to make any difference.

The CMS definitely works with IE10 and 11. You have to local issue

I have the same problem, IE 11 is rendering in document mode 7 by default, changing it to IE9, IE10 or edge solves the problem, but as soon as you close the developer toolbar, it reverts back to IE7 document mode. Is there a way to change this permanently?

Please see the FAQ item on enabling HTML5 content - you need to make a
registry modification

What you've suggested is for a client player, this is occurring on the management website not on the clients.

As a workaround, I've added the following to the index.php

header('X-UA-Compatible: IE=edge');

just above the line DEFINE('XIBO', true);

this will force edge mode in IE, but it's a bit of a hack, and I was looking for a more elegant solution.

Okay sorry. I missinderstood. It's almost certainly because you access the
CMS by a short name, so IE sees it as Intranet zone and applies the IE7
engine. You need to either use a fully qualified domain name, or change
your IE settings for the Intranet zone

I've already tried that! Just like Aaron Rich (above comment) it doesn't make any difference using the FQDN, and I've tried turning off compatibility for intranet sites. None of these work.

The only thing that works consistently is the header tag as mentioned above.

Can I just say, apart from the IE problem, the new version is a vast improvement on an already very good signage system. We've used lots of different systems like orangevalley (now defunct), signage studio (didn't want this over the internet), sedao (too expensive), onelan (too expensive), hydravision (our previous one, now defunct).

This is by far the easiest, and the best.

Thanks for all the hard work improving the code.

There's something local to your setup triggering that.

The new CMS versions work fine with IE and don't need any modifications to
the quirks mode.

If adding the tag works for you then that might be the best option, but
it's not required on a standard installation on IE 10 or 11

Great to hear you get on well with Xibo (aside from this issue) - if we could use your logo on the website, that would be great! http://xibo.org.uk/2014/08/26/xibo-trusted-by-who/

The edge tag has already been introduced in 1.7.0-alpha (still in development) as we have moved to bootstrap 3. Having it in there seems fine as a workaround.