So many problems with styling, why?
-
Here comes a rant. Why oh why is this plugin now impossible to style? I understand the need to remove the old css from the plugin, but if that is what has happened, then why is it that when I try to restyle widget elements in my child theme css, those changes are overwritten by css that is in the plugin? If you must destroy all of the styling that I had established in the prior version of the plugin, then why can’t you get your default css out of the way and let me fix it? Sometimes style choice is a matter of taste and preference, and sometimes, as in this case, it is a matter of being able to display the text on the background that I have. This is why making the style accessible to us is not a matter that should be on your future roadmap to-do list, it should have been done before the update was released. I’d like to see the documentation for how we are to make any use of the seemingly very complex classes and ids that the plugin is now made up of.
- The topic ‘So many problems with styling, why?’ is closed to new replies.