Simple question, does using a custom theme (using custom CSS) break the rules for non standard Moodle installs with moodle partners? ie if you have a custom theme with custom CSS , does that cross the line as far as what is generally regarded as "default Moodle" install? I would assume not. Your experiences welcome.
Thanks
Dom
In my experience (worked for two Moodle hosts including one partner): if customisation is contained in a plugin -- which a theme is a type of -- or in the site's settings (i.e. in the database) then that's not customisation as the Moodle source code files haven't been changed.
So if you have a custom theme (or one from the plugin directory) and needed changes made in the Custom CSS field for the theme in the site then I wouldn't expect that to be an issue.
I see. So creating and maintaining a single custom.css file in the servers usual location for the active theme would not be sufficient or allowable by a Moodle partner? is that what your suggesting Leon? (Thanks for your kind help by the way)
So creating and maintaining a single custom.css file in the servers usual location for the active theme would not be sufficient or allowable by a Moodle partner?
Obviously I can't say what partners would allow, they'll have their own policies for this. But "creating and maintaining" sounds like an overhead they won't like.
These rules get put in place because these customisations become a headache when providing support, and especially when applying updates or upgrades, so anything that hinders that is likely to meet some resistance. It's also an extra issue if you ever needed to migrate to a different host.
If you've got a third party theme that you want to customise, you could fork it to implement your requirements or ask/pay the developer to modify it as required.Dom, I think that a lot will depend upon what your moodle partner is willing to do, and it may also depend upon which theme you are using right now. (I don't use a partner.)
When I was using moodle's MORE theme, I did customize MORE with custom CSS, but this was done in a dialog box within moodle and this MORE theme. The beauty of this approach was that when I upgraded my moodle, the custom CSS persisted. Trying to customize a theme by writing custom php code could involve a few more maintenance issues when upgrading, which could bother a partner. But I would think that simply suggestion some custom CSS be put into MORE's dialog box could work, because there is little maintenance overhead.
Now I use BOOST, and I have used some custom CSS in BOOST's dialog box, and a supporting present.scss file. This involves two things. The more "things" that get added, probably the less that your partner will be willing to tolerate.
(Here is a link to my webpage that provides some resources to a presentation that I gave at MoodleMoot US.)
Hi Rick,
How are you?
To answer your question, Im pretty sure there isnt custom php just custom css that sits in the same folder as the theme used. I presume that wouldnt be a maintenance issue for moodle partners, though I know the big ones are insanely finickety (its easy to maintain a thousand cloned customer sites but not very useful for customers!)
D
Dom,
I am doing fine. Thanks for asking.
Do you know what theme you are using?