I'm fairly certain it is cached, though I don't understand the mechanism for it to be updated. If I was guessing I'd say that the theme gets refreshed every time you save the theme settings page, even if you don't change anything.
Actually I tested this and it only seems to change the number in the CSS url if you change one of the settings.
So, looks like the answer is yes.
David Scotson
Posts made by David Scotson
I believe this is a result of a bug in Moodle Core.
https://tracker.moodle.org/browse/MDL-39608
In short the form labels are supposed to grow and shrink with the screen size, but currently they grow too much at small sizes, which can push the form content into the block columns.
https://tracker.moodle.org/browse/MDL-39608
In short the form labels are supposed to grow and shrink with the screen size, but currently they grow too much at small sizes, which can push the form content into the block columns.
There's some public access courses:
About iMoot
http://2013.imoot.org/course/view.php?id=3
iMoot lounge
http://2013.imoot.org/course/view.php?id=5
but I think installing it might be the best way to check it out in depth.
About iMoot
http://2013.imoot.org/course/view.php?id=3
iMoot lounge
http://2013.imoot.org/course/view.php?id=5
but I think installing it might be the best way to check it out in depth.
Very nice! It all comes together really well to, as you say, look like it's not Moodle at all (or any CMS really) but a custom hand-crafted website, even though the look continues right into the Moodle courses. The Moodle Blocks in the footer is a particularly nice touch.
One totally unrelated question. I was looking at some of your bullet point lists to see how you were doing the icons and I saw this in the HTML:
<li id="yui_3_9_1_2_1369051526453_77"><strong>4 day</strong> long program</li>
I've seen those yui ids all over the place in Moodle before and never actually found out what they do. Does anyone happen to know? I'm a bit worried that Moodle's spending time adding ids to things via javascript for no obvious purpose.
Oh, and a quick bug report: the dropdown menus worked for me the very first time I clicked, but then didn't work after that and then didn't work at all when I tried another browser.
The main purpose of the Clean theme is to be forked as a template for new themes. Roughly 99.9% of the Clean theme is actually in a hidden parent theme called BootstrapBase rather than in Clean itself. There's nothing really in Clean so you'll still benefit from future developments as they'll be added to BootstrapBase instead.
How did you previously add the light layer of CSS to the Standard theme? If you created a new theme and then added a style sheet with fairly cosmetic changes then you can do the same for Clean if you want. You also have the option of just copying a small amount of CSS into the Clean theme settings directly, which avoids the complexity of making a theme for minor changes.
The specific change you mention (relative size of columns) is best done by changing the layout/general.php file in a new copy of Clean. Unfortunately this file is much more complex than is ideal due to the conflicting requirements of RTL, SEO, accessability, mobile-responsiveness, Bootstrap conventions and Moodle conventions. Various combinations of those work very well, but combining them all made things quite tricky.
Essentially, without getting into the reasons behind it, you'd need to change all the span classnames: span3 -> span2, span4 -> span3, span8 -> span9, span9 -> span10.
How did you previously add the light layer of CSS to the Standard theme? If you created a new theme and then added a style sheet with fairly cosmetic changes then you can do the same for Clean if you want. You also have the option of just copying a small amount of CSS into the Clean theme settings directly, which avoids the complexity of making a theme for minor changes.
The specific change you mention (relative size of columns) is best done by changing the layout/general.php file in a new copy of Clean. Unfortunately this file is much more complex than is ideal due to the conflicting requirements of RTL, SEO, accessability, mobile-responsiveness, Bootstrap conventions and Moodle conventions. Various combinations of those work very well, but combining them all made things quite tricky.
Essentially, without getting into the reasons behind it, you'd need to change all the span classnames: span3 -> span2, span4 -> span3, span8 -> span9, span9 -> span10.