by pieterh
on 02 Sep 2009 15:17
A few weeks ago I reported on a way to customize your CSS theme. Since then, some people have reported that this technique fails with IE7 and IE8. We've filed a bug report with Microsoft and my contacts there have promised "a fix before 2021, really!" So, for those unfortunate enough to try the "My Theme" technique, here's a workaround…
The problem is that IE7/IE8, being built on a superior Microsoft browsing engine, fail to recognize more than three levels of include. When they were building their engine, some dev asked the boss, "how many levels should we allow for?" and the answer was "three is enough for anyone!" Perhaps they felt that more levels would cost more. Or, maybe they just count "zero, one, two, many".
Anyhow. In that blog posting I explained, "create a custom theme called "My theme" that inherits from Base and contains this code…" This was wrong. Instead, in Appearance / Themes, select the _default category and Choose an external theme, then enter /admin:themes/code/1 and click 'save changes'. If you try to delete the "My Theme" custom theme you will get an error. Wikidot madness, don't worry about it.1
Anyone who cloned an Iron Giant template will find their clone has the same problem. Easy solution, go for it!
While we're discussing Microsoft, will-previously-known-as-the-dodgy-monkey has launched yet another fun site: UrCheatz.com which includes a section on how to hack the XBox 360 browser to handle more than three levels of CSS includes. OK, not quite, but it does have a nice cheat page for XBox GTA IV. Enjoy, and contribute your favorite cheatz!
Is that Base or Basic internal theme?
Either, or any other built-in theme, so long as you removed the reference to the custom theme.
Portfolio
If my equivalent of /admin:themes file does not contain an @IMPORT can I leave things as they are, ie continue using the custom theme?
You can probably leave it, then. As far as I can tell, two levels of nesting works, and three does not. We were at four in the rainbow themes… :-)
Portfolio
Oops! Thanks.
I do something different. I manually fix my external theme to the actual location:
http://site-name.wdfiles.com/local—files/page-name
That way, the page name is recognised as the name of the CSS file, rather than the number 1. Trivial, I know XD
By the way, Peiter, the Base theme is at the bottom of the list of the custom CSS again. I suspect a recent disaster and reversion of Wikidot software had something to do with this?
λ James Kanjo
Blog | Wikidot Expert | λ and Proud
Web Developer | HTML | CSS | JavaScript
This is neat but does not survive cloning, so is unusable in template sites (and in general, any site that might be cloned).
I saw that the Base theme had jumped to the end again and am looking for a long stick with which to beat the Wikidot git repository until it explains wtf is going on. Something got reverted, but this is the 2nd or 3rd time.
Portfolio
Poor squark.
Rob
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Strathview - Wikidot-based intranet, knowledebase and website development and management
No, it was Michal who had left a test module installed: what this did, explicitly, was renumber the themes to put Base at the end! Anyhow, that module is gone and I don't expect this zombie to rise again.
Portfolio
Poor Michal
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Strathview - Wikidot-based intranet, knowledebase and website development and management