Piotrek

@reggieofarrell @fbnxo Could you reach our Support Team, so we could take a look at your websites? We'd like to see what's going on there.

Closing it, since it's related to the old versions of Woo

@mostafa-hisham for the testing purposes we could do a PR with a filter, ultimately, it should go to the backend for unique items.

For Avada example, excluding the following scripts makes slider appear right away. The root cause is most likely inside them: ``` /wp-content/themes/Avada/includes/lib/assets/min/js/library/jquery.flexslider.js /avada/wp-includes/js/jquery/jquery.min.js /wp-content/plugins/fusion-core/js/min/avada-fusion-slider.js /wp-content/themes/Avada/includes/lib/assets/min/js/library/modernizr.js /wp-content/themes/Avada/includes/lib/assets/min/js/general/fusion.js /wp-content/themes/Avada/includes/lib/assets/min/js/library/cssua.js /wp-content/themes/Avada/includes/lib/assets/min/js/library/bootstrap.transition.js /wp-content/themes/Avada/includes/lib/assets/min/js/library/bootstrap.tooltip.js ```

@mostafa-hisham For `RUCSS Inline Attrs Exclusions` in the backend, is it possible to use wildcard (from the backend and plugin perspective)?

@vmanthos `If there isn't any used CSS in wpr_rucss_used_css to clear maybe we shouldn't display the notice.` I think that's a good enhancement for the future. `Also, when the blocking...

@CrochetFeve0251 Sorry for the wording changes... We'll go with this one: `In the server's firewall. Your host can help you with this`

Since the requirements have changed, we need the wording to be as follows: ``` It seems a security plugin or the server's firewall prevents WP Rocket from accessing the Remove...

As per discussion with @mostafa-hisham, this change won't affect RUCSS.

@Tabrisrp Yes, @mostafa-hisham mentioned that this is just enough, no other changes needed.