Hey @ulang66 – It’s because of WP Rocket caching the pages and serving cached pages which defeats the purpose of any dynamic plugins like this.
Luckily depending on the hosting environment, it may be possible to kick off our IP Location Block plugin just before “WP Rocket”, this way the requests will still be checked by IP Location Block. To do that, please set the “Validation Timing” setting to “mu-plugins”.
Some people had success with this option, but generally IP Location Block shouldn’t be used with caching plugins especially ones that does not work with the Validation Timing option.
Unfortunately, it doesn’t work for me with “mu-plugins”. I also tried the helper plugin WP Rocket | Disable Page Caching on the advice of WP Rocket support. It would work with that, but then the pages load too slowly, so I can’t use it like that. Then I probably have to assume that I have no chance to use your IP Location Block with WP Rocket, although it would certainly be a great plugin. You say it may depend on the host environment whether “mu-plugins” works. Do you know which specific settings on the host side could be responsible for this?
Hey @ulang66 – You can also read the article about caching. I know WP Rocket may not be an option but you can achieve similar results with plugins that support deferred execution and having “Validation Timing” set to “mu-plugins.php” in combination with those plugins.
https://iplocationblock.com/codex/compatibility-with-cache-plugins/
I have already read this article. I tried several caching plugins before I decided on WP Rocket. It simply had the best performance for me and caused no problems. Therefore, I can’t just replace it. Thank you for your answers. The hope would be that WP Rocket supports deferred execution one day.
