Site crashed with last update

I’m getting the exact same error on all admin pages. It’s annoying, because the code appears to just affect annoying popup messages in the backend anyway.

I replaced line 1000 in restrictcontent.php with the following and, for now, it’s working. Hopefully the devs will fix it before the next update.

    if ( ! is_admin() ) {

I am getting errors on the 2 sites I updated. I am rolling back to the previous version for now.

Hi guys,

We just pushed an update (3.2.12). Please update and let us know if you’re still experiencing this issue.

@ramilbatoy It looks like it worked! Thank you.

Hi guys,

I’m glad the latest version worked. We’re going to go ahead and mark it Resolved. Please feel free to open a new thread if any other questions come up and we’d be happy to help.

Best regards,

Same problem, now, with 3.2.13

Same here! Update to 3.2.13 crashed the site with the following fatal error in the debug log;

PHP Fatal error: Uncaught Error: Call to undefined function rcp_is_rcp_admin_page()

Didn’t update WordPress to 6.7 first though. Not sure if that will fix it, but I was in WordPress 6.6.2 still, just to be complete.

• This reply was modified 1 day, 9 hours ago by purepixels.

Solution given by @brianjohnsondesign, 4 monts ago, still works.

“replaced line 1000 in restrictcontent.php with the following and, for now, it’s working. Hopefully the devs will fix it before the next update.”

    if ( ! is_admin() ) {

Thanks for your help! I’ll try that. After I reverted to 3.2.12 I left it for now. But will try that later…

I’ve had the same problem, again. It looks like they never bothered fixing the original bug, but DID release a new version. That’s a bit surprising since they said they’d fix it.

All our plugins updated and overwrote the fix. So you just have to do it again.

For the record: I did try updating everything else first, and it did not help. The problem is exactly the same as always. My original solution still works though.

It’s a bit frustrating that they haven’t fixed this obvious bug that makes their plugin unusable, in 4 months.