Title: Update destroyed custom css
Last modified: January 7, 2020

---

# Update destroyed custom css

 *  [Sixhop](https://wordpress.org/support/users/sixhop/)
 * (@sixhop)
 * [6 years, 5 months ago](https://wordpress.org/support/topic/update-destroyed-custom-css/)
 * 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)

 *  [anoopranawat](https://wordpress.org/support/users/anoopranawat/)
 * (@anoopranawat)
 * [6 years, 5 months ago](https://wordpress.org/support/topic/update-destroyed-custom-css/#post-12310975)
 * 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](https://wordpress.org/support/users/sixhop/)
 * (@sixhop)
 * [6 years, 5 months ago](https://wordpress.org/support/topic/update-destroyed-custom-css/#post-12311412)
 * 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.
 *  [anoopranawat](https://wordpress.org/support/users/anoopranawat/)
 * (@anoopranawat)
 * [6 years, 5 months ago](https://wordpress.org/support/topic/update-destroyed-custom-css/#post-12311438)
 * Hello [@sixhop](https://wordpress.org/support/users/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.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-slick-slider-and-image-carousel_adc8e2.
   svg)
 * [WP Slick Slider and Image Carousel](https://wordpress.org/plugins/wp-slick-slider-and-image-carousel/)
 * [Support Threads](https://wordpress.org/support/plugin/wp-slick-slider-and-image-carousel/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-slick-slider-and-image-carousel/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-slick-slider-and-image-carousel/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-slick-slider-and-image-carousel/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [anoopranawat](https://wordpress.org/support/users/anoopranawat/)
 * Last activity: [6 years, 5 months ago](https://wordpress.org/support/topic/update-destroyed-custom-css/#post-12311438)