Prohibit hides all posts, disregards IDs

[WesleyanHQ]

Hi

I’m using the pro version, and for 3 of about 40 users, the Prohibit checkbox hides all posts, and disregards IDs that I added. The ID of taxonomy terms to hide posts in those.

The Allow works with taxonomy IDs, but I don’t want to use Allow because it hid something, I forget because I can’t find my notes on it. Maybe it was some categories in the edit screen it was hiding I think.

[Vladimir]

Hi,

Yes, ‘Allow’ applied to taxonomy IDs hides not only posts without allowed taxonomies, but the not allowed taxonomies too.

About users which don’t see any post. Check if there are posts with taxonomies (except prohibited IDs) which these users can edit. URE Pro hides from a restricted user any post, which this user can not edit.

If such post exists, can be edited by a user, but it’s not shown to a user according to edit restrictions you set, can you send me a little example of your posts, user permissions and edit restrictions set for him, in order I can reproduce an issue at my development environment?

[WesleyanHQ]

Okay, I will try.

Custom taxonomy, in functions.php file:

//* Create Curators Access taxonomy
add_action( 'init', 'create_divisions_tax' );
function create_divisions_tax() {
	$labels = array(
		'name'              => _x( 'Curator Access', 'taxonomy general name', 'Divi' ),
		'singular_name'     => _x( 'Curator Access', 'taxonomy singular name', 'Divi' ),
		'search_items'      => __( 'Search Curators Access', 'Divi' ),
		'all_items'         => __( 'All Curators Access', 'Divi' ),
	);
	register_taxonomy(
		'twc_divisions',
		array( 
			'post', 
			'tribe_events', 
			'page' 
		),
		array(
            'label' => __( 'Curator Access' ),
            'rewrite' => false,
			'hierarchical' => true,
		)
	);
}

Custom taxonomy applies to Posts, Pages, and Events (from Modern Tribe’s plugin).

Terms in the Curator Access taxonomy:
Admin Access Only (tag_ID is 137)
CA (tag_ID is 98)
CMAD (tag_ID is 97)
ECD (tag_ID is 100)
GP (tag_ID is 102)
GSO (tag_ID is 103)
GTO (tag_ID is 105)
WPF (tag_ID is 101)
WPH (tag_ID is 96)

User: Jane Doe
Role: Curator
Restrictions: Prohibit is checked, with category/taxonomy ID field of 96, 97, 98, 100, 101, 102, 103 which doesn’t include 105 – GTO because user is an GTO curator.

Curator role (custom role made in User Role Editor)
Role was created by copying the Editor role.
checked:
copy_posts
create_pages
create_posts
create_tablepress_tables
create_tribe_events
delete_aggregator-records
delete_others_aggregator-records
delete_others_pages
delete_others_posts
delete_others_tribe_events
delete_others_tribe_organizers
delete_others_tribe_venues
delete_pages
delete_posts
delete_private_aggregator-records
delete_private_pages
delete_private_posts
delete_private_tribe_events
delete_private_tribe_organizers
delete_private_tribe_venues
delete_published_aggregator-records
delete_published_pages
delete_published_posts
delete_published_tribe_events
delete_published_tribe_organizers
delete_published_tribe_venues
delete_tribe_events
delete_tribe_organizers
delete_tribe_venues
edit_aggregator-records
edit_others_aggregator-records
edit_others_pages
edit_others_posts
edit_others_tribe_events
edit_others_tribe_organizers
edit_others_tribe_venues
edit_pages
edit_post_subscriptions
edit_posts
edit_private_aggregator-records
edit_private_pages
edit_private_posts
edit_private_tribe_events
edit_private_tribe_organizers
edit_private_tribe_venues
edit_published_aggregator-records
edit_published_pages
edit_published_posts
edit_published_tribe_events
edit_published_tribe_organizers
edit_published_tribe_venues
edit_tribe_events
edit_tribe_organizers
edit_tribe_venues
edit_usergroups
ef_view_calendar
ef_view_story_budget
manage_categories
manage_links
moderate_comments
publish_aggregator-records
publish_pages
publish_posts
publish_tribe_events
publish_tribe_organizers
publish_tribe_venues
read
read_private_aggregator-records
read_private_pages
read_private_posts
read_private_tribe_events
read_private_tribe_organizers
read_private_tribe_venues
tablepress_access_about_screen
tablepress_access_options_screen
tablepress_add_tables
tablepress_copy_tables
tablepress_delete_tables
tablepress_edit_tables
tablepress_export_tables
tablepress_import_tables
tablepress_list_tables
unfiltered_html
upload_files

Posts:
2,606 posts total
If you go to Posts > Curator Access (in the left menu), it says 8 posts in the term GTO. There are 2 Posts, and 7 Pages, so it’s actually 9 posts that are in GTO.

Those 9 posts show up if I have Allow taxonomy ID 105
But the Categories box in the right menu of a single post edit screen is completely blank with Allow (I guess that would be correct, though it’s not what I intend to have. There are 19 categories that we currently have.)

No posts, pages, or events show up if I have Prohibit taxonomy IDs 96, 97, 98, 100, 101, 102, 103
Except a Sticky post in the taxonomy term GSO – I think because it is sticky. the ALL (0) shows as no posts, the sticky post only shows up in the tab STICKY (1) in the Posts Edit screen. There is only 1 sticky post on the website.

Let me know if you need any other info.

[Vladimir]

If you go to Posts > Curator Access (in the left menu)

What plugin provides at your site by category menu items under Posts left menu?

[Vladimir]

Please ignore my previous question.

[Vladimir]

You use at a role level ‘Prohibit’. Check if those 3 users do not have ‘Allow’ at user profile. URE takes user level settings as a primary one and in case user has ‘Allow’ at user level any role settings with ‘Prohibit’ will be ignored.

[WesleyanHQ]

Oh, at the role level? Maybe that’s what I’m missing. I was doing everything in the user profiles. Where would I find the settings for Prohibit be at the role level?

[Vladimir]

Users->User Role Editor: select role, click ‘Posts Edit’.

But if you did not use role’s level restrictions, it’s difficult to guess, what’s a reason of your problem.

Can you share a copy of files and database with me? If it does not contain any critical data of course. I will check how URE works with your site copy under PHP debugging session then.
Or may be you can reproduce a problem using test site and test data? Then share them with me?

Via DropBox, etc. Send download link to support [at-sign] role-editor.com

[WesleyanHQ]

Oh, I had not noticed that before. In the role’s level restrictions, it has Allow selected with nothing in the other fields, as I did not use it at all. Just now, I made a new role GTO Curator, and used role level restrictions, but that doesn’t work correctly either. I will see if I can get the files over to you via Dropbox.

[Vladimir]

It’s worth to mention that in case you tested the same users: restrictions set at user level are still in action. They has a priority under role level restrictions. User and role levels restrictions are combined in role level uses the same ‘block model’ (prohibit or allow) as one set for user level.

I wait your setup copy to proceed with issue reason searching.

[WesleyanHQ]

Thanks for the mention. I plan to test without plugins and with default theme, then setup a test site with the issue. It will probably be end of day before I send the update for you. Thanks for your help thus far!

[WesleyanHQ]

Okay, test site access and issue with curator role access emailed. Let me know if you need anything else to test. Thanks!

[WesleyanHQ]

Hi Vladimir, Thanks for showing me the screenshot of the test user in your own testing environment. I wanted to make sure you saw my email that your screenshot did not actually show the correct access. I’m looking for the user to have access only to GTO posts/pages/etc. Your screenshot showed access to all 86 posts. Can you confirm?

[WesleyanHQ]

To answer your very first question, I checked direct urls, and the Jane Doe user in the test webstie can access posts in GTO, while non-GTO posts are prohibited with a message, “Sorry, you are not allowed to edit this item.” BUT, access to those posts are not showing in the wp-admin Posts screen, which presents a huge problem, as already indicated.

[Vladimir]

Hi Sarah,
Thanks for this information. I continue investigate a problem.

[Author]

Posts