Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
This does not currently work right. The CSS file in the template directory gets loaded BEFORE the CSS file in the plugin directory, so the CSS file in the plugin directory still takes precedence over the GroupJive template. As a result, I still end up having to use !important statements in the template.krileon wrote: GroupJive 2.1 will allow specifying a CSS file specific to an integration within your GJ template folder. For example if you add cbgroupjiveevents.css inside your template folder it will load for the events integration allowing you to override colors if you want. You do not need to use important, you just need to add more selectors to give it more weight. At any rate important isn't a problem as works on IE7, IE8, FF, Chrome just fine.
Please Log in to join the conversation.
Load order is incorrect, will be reviewing fixing this in GJ 2.3. Currently you can just give the CSS more weight by adding more selectors.This does not currently work right. The CSS file in the template directory gets loaded BEFORE the CSS file in the plugin directory, so the CSS file in the plugin directory still takes precedence over the GroupJive template. As a result, I still end up having to use !important statements in the template.
Absolutely will not happen. They are integrations and not considered part of the core. Integrations have no business with code inside core template. Integrations are also completely optional. Forcing code to core for an integration would result in bloating.edit: I still think it's wrong to be hard-coding colour in the CSS styles of individual plugins. The plugins should inherit colour from the GroupJive template, not be imposing their own colour. Otherwise what's the point of having templates at all?
Please Log in to join the conversation.