Hi there, I would like you to know an incompatibility with the YITH WooCommerce AJAX Product Filter plugin. When it’s installed and active, the site is broken and I get the following error:

[14-Nov-2024 10:32:18 UTC] PHP Fatal error:  Uncaught Error: Call to a member function using_index_permalinks() on null in /home/_sub/dev.it/v2/wp-includes/rest-api.php:469
Stack trace:
#0 /home/_sub/dev.it/v2/wp-includes/rest-api.php(532): get_rest_url(NULL, '/', 'rest')
#1 /home/_sub/dev.it/v2/wp-content/plugins/content-control/inc/functions/compatibility.php(61): rest_url()
#2 /home/_sub/dev.it/v2/wp-content/plugins/content-control/inc/functions/compatibility.php(78): ContentControl\{closure}()
#3 /home/_sub/dev.it/v2/wp-content/plugins/content-control/classes/Controllers/Widgets.php(42): ContentControl\is_rest()
#4 /home/_sub/dev.it/v2/wp-includes/class-wp-hook.php(324): ContentControl\Controllers\Frontend\Widgets->exclude_widgets(Array)
#5 /home/_sub/dev.it/v2/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array)
#6 /home/_sub/dev.it/v2/wp-includes/widgets.php(1051): app in /home/_sub/dev.it/v2/wp-includes/rest-api.php on line 469

Disabling YITH WooCommerce AJAX Filter resolves the issue. I have already notified the Yith team.

• This topic was modified 1 week, 1 day ago by frafor.
• This topic was modified 1 week, 1 day ago by frafor.

As of WordPress 6.7, your plugin triggers the following php notice on all pages

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?content-control?domain was triggered too early

• This topic was modified 1 week, 1 day ago by justauser034675.

Hello Support, what could be the problem after creating a restriction I am getting this error?

Unexpected token '<', "<style typ"... is not valid JSON

Hi.

I’m just wondering if the Content Control works for CPT posts that have certain values for custom meta field in the CPT itself?

For example, I have CPT called Story and Chapter, in which a relational meta field ‘Chapter_Story’ inside CPT Chapter corresponds to post id of Story CPT.

For example, I want to allow access to all Chapter posts with metafield value of ‘Series A’ and ‘Series B’ to only certain roles.

Do the restriction rules cover this? At least for posts with Chapter CPT’s custom field of certain values.

When i call the rest api wp-json/wp/v2/posts?_embed all my posts are returned fine but when i add & tags=123 or categories=123 the _embedded section of the response returns:

1. 0: {code: “rest_forbidden”, message: “You do not have permission to do this.”, data: {status: 403}}
   1. code: “rest_forbidden”
   2. data: {status: 403}
   3. message: “You do not have permission to do this.”

I don’t know what has happened to this plugin, but I keep the plugin at version 1.1.10 to work properly. Versions 2.3, 2.4, 2.5 — none of them worked.

I see others having similar issues. What’s going on?

Hi, I have restricted this post to logged in users only. But the users can easily guess the url’s of the other posts that are also restricted and should NOT be seen by these logged in users. That’s because we sell 1 product (= 1 post) or 2 products (= 2 posts) etc.

How can I achieve this? Thanks!

choosing a different subscription takes the user to your website https://restrictcontentpro.com/knowledgebase/register_form/

I wasnt aware of this problem until a user contacted us, I dont know how long it has been going on

Please help fix this thank you

Hello,

I am contacting you as a last resort :(.

I am having a problem with a client site. I think the problem is directly related to Content Control.

When I deactivate it, no problem. However, as soon as I activate it, the problem occurs.

I am unable to activate the divi builder on a page or an article. The plugin goes around in circles when the Content control plugin is activated.

Have you encountered the problem? Can you help me?

PS: everything is up to date on the site, theme, plugin…

I may be missing something, since English is not my first language, but I think that You are using the term “ancestor” in the restriction editor incorrectly. I think You should use “descendant”.

Hi, thanks for keeping updating.
With v2.5.0, Post restriction in BuddyBoss(BuddyPress) Activity is now invalid. (That was valid in v2.4.0)

Is there any way to make this restriction valid by setting?
I only would like to replace excerpts message with “Override the default message” for those restricted post in BuddyBoss Activity.

Is there any policy change for those restriction?
Please confirm about that. Thanks,

Hello, I have been using the plugin on my site for several years but since the latest updates of WordPress and extensions it is impossible to activate the Divi builder.

I have a conflict with the Content Control plugin. If I deactivate it, no problem activating the builder. If I activate it, it does not work.

Have you ever encountered the problem?

Can you help me?

Thank you in advance,
Have a nice day

I’m trying to reduce the time spent executing wp_load_alloptions. I noticed that option “content_control_known_blockTypes” is one of my largest options.

AFAIK this option is only used within the wp_admin screens (e.g. settings and post editors). If so, shouln’t it be set to autoload=no. Please can function “update_block_types” be amended accordingly.

When checking why the option was so large, I noticed that it contained some block types from plugins that I no longer use. Looking through the code, I can’t see anywhere that block types are ever removed from the option. Which means the settings screen still list block types I no longer have! Would the code be better getting block types direct from WordPress. e.g. something like:

$block_types = WP_Block_Type_Registry::get_instance()->get_all_registered()

I figure I need 2 restrictions to deal with users who are not logged in when accessing a specific page:

1. Logged-out users, Redirect Login & Back, selected page
2. Logged-in users without specific role, Replace Content with my own page, selected page

But I created 2 before 1, so now I need to change Priority so that 1 is the 1st restriction – correct?

But I can’t change Priority: clicking the Up arrow in the Priority column for the Restriction does nothing. Should it? I was expecting it to move up in the list of Restrictions.

Clue: When I do Click, the Developer Console complains about “MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead.” – which is coming out of tinymce. Tried current versions of Chrome & Firefox.

I don’t think “is_post_type” is working correctly for term restrictions.

Consider the following pair of restrictions:

• 1 Internal Pages
  • General: Logged in users
  • Protection: Redirect
  • Content: “Content is Page” AND “Content is Not Home Page”
• 2 Term
  • General: Logged in users of a role, say “Author”
  • Protection: Redirect
  • Content: “Content is selected Tag = xxx”

I have a page that triggers a query involving a post_tags. When I’m logged in as a role other than “Author” I would expect the Tag xxx to be removed from the query – because of restriction 2. However, restriction 2 never gets tested. The query matches against restriction 1!

When “content_is_post_type” for “page” is called to test first part of restriction 1 for context “terms” it goes through the default branch which calls is_post_type which succeeds.

I think the switch in “content_is_post_type” needs the following additional case statement:

case 'terms':
     return false;

When using the Content Control Query Monitor display I get error:

Warning: Attempt to read property "post_title" on null in /var/www/html/wp-content/plugins/content-control/classes/QueryMonitor/Output.php on line 219 Warning: Attempt to read property "post_type" on null in /var/www/html/wp-content/plugins/content-control/classes/QueryMonitor/Output.php on line 220 

I think the problem is that user_can_view_content can be called with post_id null. So get_post( $post_id ) in “output_post_restrictions” will return null in these cases. Hence, the warning message.

Restricting content with “Content is a Post with Category” works as expected. But I need “Content is a Page with Category” – which is not an option (I assume, because WP does not support page categories without a plugin).

So, any ideas how I could restrict pages by category?

And what is the purpose of “Content is A Selected Category”? What is an example of content that option would restrict?

Noticed the following error in my system log:

Trying to access array offset on value of type null in ..../public_html/wp-content/plugins/content-control/inc/functions/rule-callbacks.php on line 520

If “get_rest_api_intent” is called when global “rest_intent” is null there is code to calculate and set the value of global “rest_intent”. However, the value passed to the return statement apply_filter is the old null value NOT the new calculated value. So I think null will be passed back in this case, causing the error above.

Somewhere between version 2.1.0 and 2.4.0 the code for get_post_type_tax_rules has been modified to include:

// Skip taxonomies that are not public.
$should_skip_private_tax = ! plugin()->get_option( 'includePrivateTaxonomies', false );

As a result any rules previously defined using private taxonomies stop working.

The setting ‘includePrivateTaxonomies’ does not appear to be exposed on the Settings UI.

To avoid breaking existing installations this setting should probably default to true rather than false.

It looks like I can workaround the problem by setting ‘includePrivateTaxonomies’ in ‘content_control_settings’ option to true.

Hi

I’ve used Content control for my site for a long time. All the site is protected but some pages for wich a special template has been prepared. So all pages or any other content are redirected to the login page, but this template pages are open to anyonce.

Since the latest update this is not working, and now also the pages with the selected template are being redirected to login.

The picture below is how my site was set in the previoues version, that worked fine. After updating the plug (the had do do a database rebuild), the template option is not working.

Could you help me?

Thanks, Marcos

Hello team! So basically what I want to do is to hide groups. So non logged in users should be able to access that page: https://primary-portal.gr/omades/ but then when they click on a single team they get redirected.

So what’s the restriction type for that? I tried several but none worked..

You gonna save me, thanks!

Hi, Content Control Version 2.4.0 is not working well with BuddyPress(BuddyBoss).
The activity feed of BuddyBoss is not shown, when I set contents restriction “Post with Tag”.

BuddyPress(BuddyBoss) uses Post for activity feed, and it seems Content Control restrict those activity feeds to be shown, even the restriction condition is not meet.

With version 2.2.8, there are no problem. (I won’t use 2.3.0, because there are huge issue with it)
Probably, the error I reported, maybe related to the issue here.

Would you check the issue please? BuddyPress Activity feeds should not be restricted with Restriction rule “Post”.

Thanks,

Hi, sometimes I have following error.
Would you check and solve the error?
Please let me know, if there are something that I can check.

Error Type: E_ERROR

Error Message:

Uncaught Error: Call to a member function get_message() on bool in /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/content-control/classes/Controllers/Frontend/Restrictions/PostContent.php:170

Stack trace:

Uncaught Error: Call to a member function get_message() on bool in /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/content-control/classes/Controllers/Frontend/Restrictions/PostContent.php:170
Stack trace:
#0 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/class-wp-hook.php(324): ContentControl\Controllers\Frontend\Restrictions\PostContent->filter_the_excerpt_if_restricted('2023\xE5\xB9\xB4\xE5\xBA\xA6\xE3\x81\x8C\xE3\x83...', Object(WP_Post))
#1 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters('2023\xE5\xB9\xB4\xE5\xBA\xA6\xE3\x81\x8C\xE3\x83...', Array)
#2 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/post-template.php(434): apply_filters('get_the_excerpt', '', Object(WP_Post))
#3 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-activity/bp-activity-filters.php(2691): get_the_excerpt(Object(WP_Post))
#4 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/class-wp-hook.php(324): bp_blogs_activity_content_with_read_more('', Object(stdClass))
#5 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/plugin.php(256): WP_Hook->apply_filters('', Array)
#6 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-activity/bp-activity-template.php(1427): apply_filters_ref_array('bp_get_activity...', Array)
#7 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-activity/bp-activity-template.php(1394): bp_get_activity_content_body()
#8 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-templates/bp-nouveau/includes/activity/template-tags.php(217): bp_activity_content_body()
#9 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/themes/buddyboss-theme/buddypress/activity/entry.php(185): bp_nouveau_activity_content()
#10 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/template.php(812): require('/home/minamisaw...')
#11 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-core/bp-core-template-loader.php(180): load_template('/home/minamisaw...', false, Array)
#12 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-core/bp-core-template-loader.php(70): bp_locate_template(Array, true, false, Array)
#13 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-templates/bp-nouveau/buddypress/activity/activity-loop.php(23): bp_get_template_part('activity/entry')
#14 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/template.php(810): require_once('/home/minamisaw...')
#15 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-content/plugins/buddyboss-platform/bp-templates/bp-nouveau/includes/ajax.php(140): load_template('/home/minamisaw...')
#16 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/class-wp-hook.php(324): bp_nouveau_ajax_object_template_loader('')
#17 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#18 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#19 /home/minamisawa/jiyu-minamisawa.jp/public_html/wp-admin/admin-ajax.php(207): do_action('wp_ajax_nopriv_...')
#20 {main}
thrown

Hello getting more disputes here, one thing the bank requires is that we allow the user to scroll through the terms then accept, but this only opens a link to the terms. We have stated some of the terms at signup but according to the bank we need a scroll then accept function to win a dispute

Also there are no customer signatures when they pay for a service, I am not sure what to provide them as this

Refund and cancellation policy also would be nice, although I have it in terms, they require this

I included a link to Stripe dispute process

I have explained the subscription is automatically renewed until the customer manually cancels the subscription

Do you have any other tools I can use to help win a renewed subscription dispute ?

Thank you

I’ve used this plugin for some time now, and been very happy with it. The latest update has errors though. Viewing restricted pages normally causes the WordPress login box to show, with version 2.4.0 the site displayed some pages that it shouldn’t, unless logged in. Rolling back to v2.3.0 corrected the issue. Auto-updates now turned off.

There is a negative review dating back to June 10 that I assume is connected with the same issue, as I’ve never had problems before.

Hello

I am testing this plugin on a test site. I am really happy that it recognises the other plugins I have installed and their capabilities, because this allows me to restrict them using the rules.

I have a plugin that lets users publish listings (like on a classifieds website) on the front end. I created 2 test categories, called “one” and “two”. I would like to restrict everything in category “two” from being seen by logged out users and only show to certain logged in users by their role. The plugin can do all this, but the problem is, when I select hide content if “Content Is A Listing with Category”, it asks me to select/type in the category but when I type it in, it says “No suggestions” and no cateogries are listed so I cannot actually select the category I want to hide.

Can you assist?

Thanks.

Hi

You can restrict access for a specific tag but not for a specific category for the event calendar. Is that correct? Now I use tags but it would be more user friendly to let me select a specific event category to hide.

Thank you!

It’s the time of year for renewals, but we’re encountering several issues with Stripe, such as:

• “Suspicious”
• “Try again later”
• “Transaction not allowed”
• “Do not honor”
• “Early fraud warning”

While some errors are understandable, these particular messages are not. I have already contacted Stripe Support, and they advised me to reach out to you for further assistance.

What could be the cause of these issues?

I sincerely appreciate any help you can provide.

On one of my pages I have a sign-in block which is set to display for logged out users only (screenshot).

However the sign in block still displays for admins on the front-end, which it did not before. This is pretty confusing for admin users as it still shows the logged out content. I would expect that in the editor, not but not on the front-end.

I tested with a non-admin account and it works as expected.

Hello, maybe the last version created a white screen on the website on a client.
I deactivated it, and the user can log again.

It’s linked to the last version. Can’t help more.

• This topic was modified 5 months, 3 weeks ago by pixluser.