Content Control stopped working

@rogererkens – Sorry to hear that. Backwards isn’t the way to go so let’s see if we can’t help you work out any kinks in the new version.

1. Our new editor uses react and the Rest api. Because of this when editing a restriction, at first it might only show numbers for your selected items, but that is because it has to load the page/post titles from the Rest API. They should replace with text as soon as that happens. If not it would generally mean those items either no longer exist or there was an error of some kind fetching them from the Rest API
2. Rules were always done by ID, so that shouldn’t break functionality.
   

Can you tell me in detail how you have it set up, what you expect to happen and what is actually happening?

Hi Daniel,

I have set up 4 rules that determine which pages Logged in User have access to. All rules state that some userroles have access to some pages. The pages are selected with the rule “Is a selected page”. In the old version this workes fine. When some tries to open a page that is restricted they get a message that this content is not accessible for them. We use User defined menus also so Content Control is only to prevent someone entering the page manual by typing the link in the addressbar of the browser.
After updating to the new version the rules just don’t work anymore. These are the same rules. In first instance I updated from 1.1.10 to version 2.0.5. From there I got some database message about updating. After clicking it, it took ages to complete. After a while the old rules from version 1.1.10 came back. But they did not work. Pages were accessible. I tried to make some new rules to test it, but they did not worked either.

for what it’s worth, I’m having almost the exact same problem on my site. I only use 1 rule to protect roughly 5 pages using the same “is a selected page”. It used to be great, now it doesn’t protect the page. I tried recreating the rule, and still have the same result.
I also tried updating the plugin and got a weird error at first, but then after I tried again, the error wasnt there. It shows that Im using v2.0.6.
Clearly this isn’t isolated to your installation…

@rogererkens, @rabbit424 – Can you follow?this guide?and send us a token via the?support form here. Leave a link to this ticket in the message so I can find it easily.

Will check things over and see if we can’t work out the kinks for you.

@rogererkens, @rabbit424 – Can you both try the latest version, it fixed a bug where content replacement wasn’t always being triggered. Now its the default fallback if no other protection method got applied.

I just tried to update to the latest version but then my wp-admin crashed. After disabling the plugin I regained access. I have gone back again to the old version. Tomorrow I will do some more testing in a staging website.

@rogererkens – Oh no, sorry to hear that. I haven’t had any other reports of fatal errors in nearly 4-5 days.

Would it be possible for you to at least post the php error logs for that error.

You can usually find them from your hosting dash/panel.

Hi Daniel,

This seems to be the one:

AH01071: Got error ‘PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home/nmwo.nl/public_html/phhn.nl/wp-content/plugins/content-control/classes/Plugin/Logging.php on line 400PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81920 bytes) in /home/nmwo.nl/public_html/phhn.nl/wp-includes/option.php on line 562′, referer: https://www.phhn.nl/wp-admin/

So it seems to be a memory issue?

@rogererkens – Try adding this code to your themes functions.php or to your wp-config.php file

define( 'CONTENT_CONTROL_DISABLE_LOGGING', true );

If the error goes away let me know, it means we need to track down why your logs are either filling up, already filled up before, or are for some reason not loadable/saveable/operating in the expected way.

I have the exact same issue. Everything stopped being restricted on the latest update and I had to go back to 1.1.10 to get it all working again.

@blafoley – Can you start a new thread with full details of your issue, thats the best way to ensure yours gets solved. Based on just the limited info provided, there is no way to know if your issue is related to the ones faced by this thread or not.

@rogererkens – Can you clarify if your site uses any caching that might need to be considered?

Also does it use any translation plugins or similar where content is duplicated in any way?

Want to get to the bottom of your issue, but with limited info through back & forth it is not going as quickly as we’d like.

Are you able to grant access to a staging site with the issue? If so can you follow this guide and submit the token via the support form on our site?

Alternatively if you can you recreate the issue on one of our free demo sites we can use that to troubleshoot more closely. You can install any plugins needed to replicate it there, then just ping us the url.

Hi Daniel,

I have not had any time yet to add the code to the functions file or the wp-config file.
At the moment we are using WP fastest cache on this website. But the first thing I do when a plugin causes trouble is turn the caching of.

i will try to add the code asap and then uodate to the latest version. If it still does not work I will create a staging site with the issue and grant access ro you.

We are also experiencing an issue with your plugin after updating from version 1.1.9 to version 2.0.9.

We get a blank page when we click on the “Content Control” option on the admin side. We don’t see any of the rules that we configured. Also, on the plugins page, we see a message that reads, “Content Control has been updated and needs to run some database upgrades.” We see a blank page when we click the “Upgrade Now” button.
We are running the latest version of WordPress 6.3.1. We are using PHP 7.4.33 and MySQL 10.5.22-MariaDB.

Thanks.

@ogagliardijr – Sorry to hear that. It sounds like your having a different type of issue and should probably start a new thread, but while your at it, go ahead and use this guide on that empty page as you likely have a JS error in your admin of some kind: https://docs.wppopupmaker.com/article/373-checking-javascript-errors

@rogererkens – Keep me posted.