Hi graftedin,
Let me check with my developer about the specifics of that…I’ll get back to you.
HI graftedin,
Here’s what my developer had to say:
If its que’d after then it overrides my style corrections.
Does this mean he added CSS rules to modify how AWPCP looks by default? If that’s the case, then is going to be user to:
Use the plugin’s custom stylesheet feature, or
Update the plugin to look for the custom stylesheet in the active theme’s directory.
If, however, AWPCP’s stylesheet is overwriting CSS rules defined in the theme’s stylesheet, and those rules are not related to AWPCP, then that’s a bug and we need to update our CSS to stop doing that.
Could you please forward my question above to the user, so that we can understand the situation better and decide what to do?
Please let me know.
I added rules to my theme’s css that should override the plugin’s css as long as the plugin’s css isn’t cue’d after the theme’s.
If your goal is to override the plugin’s CSS always, then we would suggest using a custom CSS file through AWPCP.
Here is an article about how to use custom CSS with AWPCP in a way that doesn’t get overwritten on upgrade of AWPCP: http://awpcp.com/forum/faq/how-to-use-custom-styles-with-awpcp/
This is ALWAYS guaranteed to be loaded before ours, and has nothing to do with the theme CSS load order…it’s probably easier to push your changes in there.
Can you please try that?
I’d rather stick to using my theme’s (child theme’s) css so I don’t have customizations scattered through out multiple files.
I have this current situation solved so its not a big deal. I was just hoping that for future upgrades there would be a way to force the awpcp css to not cue after the theme’s.
