• I’ve used another alert bar notification plug-in for over a year (review here: https://wordpress.org/support/view/plugin-reviews/gc-message-bar?filter=1) but it included lots of tracking and analytics options that I just didn’t use. When cleaning my DB I found it had stuffed a whole bunch of crud that was slowing it down.

    I was on the hunt for a recently made alert bar and before I got to this one I saw a couple of promising ones. But once I finished reading all of the features they all had a message saying that some of the features listed were not available in the non-premium version.

    Well, this plug-in does not HAVE a premium version. It really does do what it says it does and it does it without all of the fluff.

    BUT ….

    I do wish that the plugin authors had written the plug-in using standard WordPress Protocols (ie using enqueue for calling the JS and CSS scripts) because my CDN service cannot find, combine or minimize these files and downloading them on every page adds a full second to my page load times.

    If they should make such a change – I will gladly come back and give this plug-in five stars (because other than this issue it deserves it!!)

Viewing 1 replies (of 1 total)
  • Plugin Author Syam Mohan

    (@syammohanm)

    Thank you for the review.

    This plugin does uses the standard WordPress functions to inject CSS and JavaScript. Search for wpfront-notification-bar.css and wpfront-notification-bar.js in your page source to find the static files.

    With that said there is one place where it doesn’t use the standard function and that is what you are referring in this review. There are two main reasons why it doesn’t go as part of those files.

    1. Those are dynamic CSS and there is no easy way in WordPress to append/add dynamic CSS to a static CSS file.
    2. Since those values come from user entries, plugin need to work around browser caching (append dynamic values to URL, etc.).

    There is also an issue with CSS precedence but its a small issue and will need to be handled by the user, but that means more support questions for me.

    So the decision was made based on a trade off between more development time and support time vs a few extra lines on the page source.

    The content added into your page source is less than 1kb and with HTTP compression, the data that sends as part of your response is hardly nothing. If those few lines increases your response time by one second, then you are going to hit with a long delay on a pages/posts with really long content. You can also try some caching plugin to increase your response time (They usually convert dynamic content into static files).

    Sorry for the delayed response.

    Thanks

Viewing 1 replies (of 1 total)

The topic ‘Works – without having to buy “premium options” BUT…’ is closed to new replies.