• With the update from 1.8 to 1.9, there were changes in css classes. Result: Customer´s sites looked strange, lots of work fixing this.
    Well, we stopped using slick slider.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Anoop Ranawat

    (@anoopranawat)

    Hello,

    I am really sorry for the issue that you were facing.
    Please always update any plugin after checking the change-log. As i our latest update our change log was :

    1.9.1 (26, Dec 2019)
    [*] Updated features list.
    [*] Replaced wp_reset_query() with wp_reset_postdata()
    [*] Added prefix wpsisac- to all classes in css to avoid conflict with any theme and third-party plugins.

    Where we have added the note ie Added prefix wpsisac- to all classes in css to avoid conflict with any theme and third-party plugins.

    If you need our help, please let us know 🙂

    Thread Starter Sixhop

    (@sixhop)

    Thank you for your answer.
    Still, how does that help me?
    When the plugin author changes css classes, I have 3 choices:

    • to update the plugin and change all css files
    • not update the plugin
    • switch to different plugin
    • I always want to keep all plugins updated to the most current version for safety reasons. So, only 2 choices left. I opted to switch plugin and was glad I had been running slick slider on only few websites.

    Plugin Author Anoop Ranawat

    (@anoopranawat)

    Hello @sixhop,

    I can understand your concern but some time we also need to take care to avoid the conflict 🙂 . if you have added a custom css then you can just add the prefix to the css classes that we have added.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Update destroyed custom css’ is closed to new replies.