Revert

Hi @terry2124,

That’s unusual. Content Control restrictions are disabled when the plugin is deactivated or deleted. Do you have caching mechanisms in place (plugin or hosting?

We’ll wait for your response.

I could not reverse it. After removing the conditions, changing the conditions and even adding conditions to allow all nothing changed. Removed the plugin and deleted the folder and still nothing. I had to do a full file restore and still no go, I did a full database backup after that and my site was then ok.

Yes, I do use caching but I made sure to purge the cache from the server, lightspeed addon which is connected to the server, Cloudflare was purged and my web browser. Did the purges several times and waited a good amount of time.

The Content Control plugin worked well but removing it was an issue because the rules always stayed in effect even without the plugin and files present, my guess is that it was something with the database.

@terry2124 – Based on what you’ve stated, the only conclusion I can draw is your browser or dns cache locally on your own machine may have memorized the redirects, only way to clear that is flushing dns and clearing browser cache/history to clear the redirects.

That said I want to clear up the technical possibilities:

• If our plugin’s code is not both installed and active, the redirects are not coming from it. This is simply how WordPress works, not something we set up.
• There are no stored files, no redirect lists in the database, they are processed live as the page is requested. We compare content being rendered to the rules you set and redirect if they match.
• The only way php file can be used after deleted is if its already in opcache that never expires, not ideal. But this also means your db is perma cached as well since again, installed & active, and active status comes from wp_options table.
• There are other plugins that provide similar redirect/protection under different guises, such as membership plugins, seo redirect managers. Its possible the redirect in question never came from our plugin to begin with.

Happy to try and debug for you, but given the files aren’t even installed, there is pretty much 0% chance our plugin is causing it now given all the steps you said you already tried.