A Few Glitches, But Overall a Good Plugin

  • There are too many “!important” CSS classes and too much inline CSS. This is more difficult than it needs to be to override. In fact, it requires me to edit the plugin CSS file after every upgrade.

    Other than this, Easing Slider works great.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author MatthewRuddy

    (@matthewruddy)

    Hi Brad, thanks for the feedback ?? The “!important” rulings are needed to ensure a high compatibility rate between Easing Slider and other themes. We’ve often found themes (not always the best ones) to add styling undesirably to the slider elements and thus break it. In forcing a lot of the core structural CSS, we’ve reduced related support requests significantly.

    For example, CSS like this would cause issues when displaying a slider in a post. This would be typical CSS to handle responsive images in a post’s content.

    .entry-content img {
   max-width: 50%;
}

    Sadly that’s just a caveat working with WordPress and having a front-end plugin. If we removed these rulings, we’d break the plugin visually for a lot of users, which in turn would put major stress on the free support we already provide ??

    I’ve tried my best to keep the “!important” rulings to essentially properties where possible. Soon I’ll be implementing a template loader, so you can use your own HTML for the various Easing Slider properties instead ??

    Thanks again for your kind words and feedback!

    Thread Starter Brad West

    (@bradawest)

    I had not considered these issues. I’ll be looking forward to the template loader. Hopefully that will resolve the problem of editing the CSS file after every update.

    Keep up the good work over there.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘A Few Glitches, But Overall a Good Plugin’ is closed to new replies.