[Vladimir]

Hi,

Unfortunately, I did not find a solution for today. I will make the few tries more though.

[Vladimir]

I found that “Advance Custom Fields” plugin stores its custom fields data as the custom post type ‘acf-field’. This may be a problem, why some of revisioned values of such fields were not available when URE applied edit restrictions by the list of the post ID, as ‘acf-field’ custom post type was not included into the list of records available for the current user.

I added ‘acf-field’ custom post type to the arguments list of the code at your functions.php file:

$posts = get_posts(array(
	'numberposts'	=> -1,
	'post_type'		=> array('tribe_events','page','revision','acf-field'),
	'post_status'   => 'any',
	'meta_query'	=> array(
		'relation'		=> 'OR',
		array(
			'key'	 	=> 'analytics_group_name',
			'value'	  	=> $ag,
			'compare' 	=> 'IN',
			),		
		),
	));

As you use revisions, I added revision post type too and replaced post status to ‘any’ (revision has ‘inherit’ post status’).

Restricted user sees the latest content now at my test site. Make a new test at your own.

[Vladimir]

I reproduced and investigate now some of the described problems with content versioning/revisions.

The conflict takes place between code which restricts edit access by pages ID list and Advanced Custom Fields which shows the latest content for the ‘draft’ page, when the edit restrictions were switched off, and shows some older cached content when edit restrictions are active.

I did not find solution to the moment and continue working on this problem.

[Vladimir]

Thanks for the detailed description. I will try to reproduce and investigate this.

[Vladimir]

“Admin menu” dialog show admin menu items according to the selected role permissions. In order to see “Appearance” menu there role should can at least “edit_theme_options”.

[Vladimir]

Hi,

@localmediach, what do you see at the subsite “Admin menu” when you open it for the same role, no any checkboxes selected?

If that’s applicable, you may send superadmin credentials to support [at-sign] role-editor.com, I will look what is going wrong.

[Vladimir]

URE Pro does not offer any custom solution to control Divi modules visibility.

[Vladimir]

Hi,

All menu items added by this plugin are protected by ‘manage_options’ user capability.
It’s possible to replace it via custom filter 'wpum_admin_pages_capability'.

[Vladimir]

Hi ataeipour,

You can add such code to the functions.php file of your active theme.

[Vladimir]

Hi Till,

There is no such ‘read’ capability for the custom post types. You can restrict view for th selected posts using “Posts view access” add-on.

[Vladimir]

No, we don’t offer any affiliate program.

[Vladimir]

Current URE Pro version does not support edit restrictions for CF7 plugin.

CF7 uses custom UI page to show forms list. URE Pro simply does not apply edit restrictions for the page ‘admin.php?page=wpcf7’.

More, CF7 uses meta capabilities:

	$meta_caps = array(
		'wpcf7_edit_contact_form' => WPCF7_ADMIN_READ_WRITE_CAPABILITY,
		'wpcf7_edit_contact_forms' => WPCF7_ADMIN_READ_WRITE_CAPABILITY,
		'wpcf7_read_contact_form' => WPCF7_ADMIN_READ_CAPABILITY,
		'wpcf7_read_contact_forms' => WPCF7_ADMIN_READ_CAPABILITY,
		'wpcf7_delete_contact_form' => WPCF7_ADMIN_READ_WRITE_CAPABILITY,
		'wpcf7_delete_contact_forms' => WPCF7_ADMIN_READ_WRITE_CAPABILITY,
		'wpcf7_manage_integration' => 'manage_options',
		'wpcf7_submit' => 'read',
	);

And while really it needs to check ‘publish_pages’ instead of ‘wpcf7_edit_contact_forms’, WordPress function ‘user_can’ used by URE Pro check directly ‘wpcf7_edit_contact_forms’. So solutions is not so easy. I will try to search workaround.

[Vladimir]

Hi Jon,

Try the beta version 4.60.b1. It’s available after login from the same “Download” page.

[Vladimir]

You can place images to some external resource and send here the links. Or send screenshots directly to support [at-sign] role-editor.com

[Vladimir]

Hi,

Starting from version 4.59.2 URE

* Update: Option “Force custom post types to use their own capabilities” replaces default capabilities for the custom taxonomies also.
It takes the slug of the 1st post type associated with such taxonomy (e.g. ‘video’) and builds own capabilities this way: manage_terms->manage_video_terms, edit_terms->edit_video_terms, delete_terms->delete_video_terms, assign_terms->assign_video_terms.

So search between custom capabilities similar to the named above, but with your custom post type inside and grant them to your role.

[Author]

Posts