Support » Plugin: Sitewide Notice WP » Trouble with caching?

  • Resolved thecueball


    Does the plugin have any issue with Redis caching? Trying out now and it works really well with PMPro on our dev site, but not on our live one :/

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Carlo


    Hello @thecueball

    Thank you for using Sitewide Notice WP. Sorry to hear about the issue you are facing.

    I’m not aware that Sitewide Notice WP has caching problems. Can you elaborate on what is not working, so we can look into it further on our side.

    Thanks Carlo – we’ve got the plugin running on our dev site (, which is identical to our live site ( For some reason the header injection isn’t appearing on the live site though, and the only real difference is that live is running Redis. It’s not been an issue with other plugins that inject into the header though, so not sure what’s conflicting.

    PMPro is on both sites, including the limit page view addon.

    Plugin Support Carlo


    @thecueball thank you for the feedback. Can you clear the cache to test if that is the problem? It does seem like the plugin is not active on the live site at the moment?

    @carlo Thanks – we’ve purged the cache and can see that it’s now appearing in the header, but we can’t update the message without clearing the cache again.

    Plugin Author Andrew Lima


    Hi @thecueball

    I’ve looked into this further, we store the banner settings in an array inside the options table.

    The function update_option stores these values in the cache as we don’t set the $autoload to false. I’d advise against adjusting this as each load would hit your database on every page load and cause strain on your site (especially a site of your size – if your site had a low visitor count you could get away with it).

    Do you plan on updating the contents of the banner regularly? You may need to customize this further – please feel free to fork the plugin and adjust it to your needs to work around your caching issue.

    We won’t be adding in a workaround to bypass the cache due to performance issues this would cause (It’d create a ton of support from our end).

    Thank you for understanding.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.