having asked the author of the weaver theme about the calendar display someone found the problem and this is what they said
OK, so I looked in more details, and both Weaver II and Xtreme will have some level of interference with the plugin styling, although less with Xtreme.
Here is what is going on and what can be done about it
The issue I see, is that if most of the theme table rules are simple tr td selector, but there are a couple that use #content tr td as a selector.
The use of #content makes these rule override any specialized rule from the plugin developer that does not use an ID selector.
The plugin here is using very specific rules but they don’t use an ID as selector, therefore the theme rule that use #content tr td end up overriding them.
The plugin tables are inside a container that has the ID #wpfc-calendar , so the what the plugin developer should have done, is add that selector in front of all his current rules, to enforce the rules inside his own container.
That being said, @weaver, I think that using #content may be too strong.
If content was needed in weaver II this is the only option, but in Xtreme, the rule could use .content tr td instead which would be less strong and allow any specialized rule from the plugin to win.
Another solution would be to add a Table style for “No Styling” with no theme rules for tables at all, so no possible interaction.
@dsg257
In the mean time, we can fix your issue in either weaver II or Xtreme (redoing some of the plugin rules with better selectors), but it will be easier in Xtreme as Weaver II generates the stronger rule for both border and padding (which causes the most damage), when in Xtreme if you select “No Border” in Main options > Content Areas > List <HR> tables > Table styles, the only overriding rule using #content will be for borders, so we will have less plugin rules to redo.
But you need to inform the plugin developer that as his plugin stands, his CSS is too weak, and that all his plugin rules should use the selector #wpfc-calendar so they can override any default theme rules. If (as he should 🙂 ) he agrees to do that, it will solve the problem without any custom CSS on the weaver side.
i hope this makes sense you you and can fix the problem
