WP Page Navi CSS
-
(Merged Threads)
@ soapy,
I merged these threads because they basically deal with the same thing.
What’s your URL so I can test?
EDIT: Looking at your import statement, I think it’s wrong. Since the new css file is located in the root of your child theme folder, I think you need to come up two levels.
Try this:
@import url("../../plugins/wp-pagenavi/pagenavi-css.css");
ModActually, you don’t need to import the css from a plugin at all, since the plugin will still add its style sheet. Just copy those portions you want to change and paste them to your child theme style sheet and make modifications.
So the child theme stylesheet adjustments will overwrite any plugin stylesheet properties?
ModProvided that the child theme style sheet gets loaded after the plugin stylesheet, yes. Some time ago, I wrote a post in a thread explaining the order that stylesheets get loaded in. I’ve been looking for it, but can’t find it. In general, plugins (good ones, at least) load their stylesheets first, and then the theme’s stylesheet. This allows a theme to override those settings.
Most plugins use very specific id’s and classes so that themes don’t accidentally use the same CSS and overwrite their styling for this very reason.
Most plugins use very specific id’s and classes
I’ve noticed that as well. I’ve learned to name all mine, including functions, with the prefix
jwl
, my initials.I’ll look into the stylesheet order of loading. This would be good to know.
So what’s the best way to keep threads easy to find in searches? Is it the tags? Should I get into the habit of adding specific tags to each post?
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.