CSS Class Conflicts

Forums › Forums › Search & Filter Pro › CSS Class Conflicts

Viewing 4 posts – 1 through 4 (of 4 total)
  • Anonymous
    #30756

    SF uses css classes that should be reserved for default WordPress styling. For example, I am loading the default Jquery accordion and tabs scripts to organize some data on my site. The page has zero search and filter functionality. But since SF uses class such as ui-widget-content or ui-corner-bottom, SF loads styling in a place that it should not. When you load the jquery scripts, it targets an ID then loads default classes to that div. They are the default for WordPress Core. SF should prefix their classes so that it does not override/conflict with WordPress Core.

    I have a screenshot of Google Chrome Inspector if you want to see the code. The highlighted HTML is the default css classes loaded by the tabs jqery. And on the right hand side, you can see SF loading 2 different styles (ui-corner-bottom and ui-widget-content).

    Ross Moderator
    #30758

    Hi Clayton

    What version of S&F are you using? Since 2.0, all class names have prefixes.

    Thanks

    Anonymous
    #30763

    Sorry about that. I thought I had the most recent version. Just checked and I was using 1.4.1. Just upgraded and my issue is resolved. Thanks for the quick reply…I really like your plugin btw.

    Ross Moderator
    #30764

    Thanks! 🙂

Viewing 4 posts – 1 through 4 (of 4 total)

Search & Filter Support
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

We also use cookies to store items in your cart as well as allowing your to login on the site.

You can adjust all of your cookie settings by navigating the tabs on the left hand side.

By continuing to use this site, you also agree to our Privacy Policy.