The same thing happened to me, you have to go back to the previous version.

The same here on our homepage. Error message:

Attempt to read property "ID" on null in (...)/wp-content/plugins/restrict-content/legacy/includes/display-functions.php on line 106

I’m also seeing a fatal error when updating:

Fatal error: Uncaught Error: Call to undefined function rcp_is_rcp_admin_page() in /wp-content/plugins/restrict-content/restrictcontent.php:1000 Stack trace: #0 /wp-includes/class-wp-hook.php(324): {closure}() #1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /wp-includes/plugin.php(517): WP_Hook->do_action() #3 /wp-admin/admin-header.php(303): do_action() #4 /wp-admin/admin.php(239): require_once(‘…’) #5 {main} thrown in /wp-content/plugins/restrict-content/restrictcontent.php on line 1000

This error i get if i try to fix the error in display-functions.php like this:

global $rc_options;
 global $post;

if (is_null($post->ID)) {
    return $content;
}

$rcp_user_level = get_post_meta( $post->ID, 'rcp_user_level', true );
(...)

Currently the only way is a downdate to v3.2.10 here: https://wordpress.org/plugins/restrict-content/advanced/

  • This reply was modified 1 year, 9 months ago by filout.
  • This reply was modified 1 year, 9 months ago by filout.

Same here. I’m on php 7.4.
This is the error I’m getting:

Fatal error: Uncaught Error: Call to undefined function rcp_is_rcp_admin_page() in /wp-content/plugins/restrict-content/restrictcontent.php:1000 Stack trace: #0 /wp-includes/class-wp-hook.php(324): {closure}(”) #1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #2 /wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /wp-admin/admin-header.php(303): do_action(‘admin_notices’) #4 /wp-admin/admin.php(239): require_once(‘/…’) #5 {main} thrown in /wp-content/plugins/restrict-content/restrictcontent.php on line 1000

@filout Thank you for sharing the link to the old version. This worked for me:

Currently the only way is a downgrade to v3.2.10 here: https://wordpress.org/plugins/restrict-content/advanced/

Thanks for the help. Hopefully they can fix the current version.

This plugin provides a fundamental aspect of our website, restricting members only access. I hope there will be un updated version soon that works so I can make the website live again. Either that or find an alternative plugin? Any suggestions from anyone would be most appreciated.

Problem is a sales banner they’ve added to wp-content/plugins/restrict-content/restrictcontent.php

Go to theend of the file (around line 1000) and delete everything after the line that reads:

add_action(‘admin_notices’, ‘restrict_content_bfcm_notice’);

(Keep that line. Delete all that follows.)

That got my site back up and running…

Hello everybody!

I just wanted to let you all know that we are currently working hard to figure this out. In my testing, I am not able to reproduce this at all, so currently we’re trying to figure out why so many of you all are experiencing this but not everybody is.

If any of you think you might know something about your specific setup that you think might be relevant please don’t hesitate to share it.

Also, please try this:

Please let me know if you’re still getting a fatal error after this.

**UPDATE**

It appears this issue is only happening to folks who are using legacy mode.

We’re close to releasing a fix for this.

**UPDATE**

we just pushed an update. Please update and let us know if you’re still experiencing this issue.

Updated and got the following message:

Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/webvol8/ka/gpzgf1xxkwtes1r/domsand.org/public_html/wp-includes/functions.php on line 7300

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/webvol8/ka/gpzgf1xxkwtes1r/domsand.org/public_html/wp-includes/functions.php on line 2189

login-page for members still not working, get a 404 (page can’t be found)

  • This reply was modified 1 year, 9 months ago by johanliden.

@johanliden as that is not related to this ticket, please open a new ticket so someone can help you investigate that =]