[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.

[Vladimir]

Hi Jon,

I will publish the updated version this month.

[Vladimir]

Hi Jon,

There is no such hook currently. You can just comment the line, which initiates the related code:
wp-content/plugins/user-role-editor-pro/pro/includes/classes/user-role-editor-pro.php, line # 35 ( // $this->init_updater(); ) :

    protected function __construct() {
        $this->lib = URE_Lib_Pro::get_instance('user_role_editor');
        
        add_action('ure_on_activation', array($this, 'execute_once'));
        parent::__construct();                                        

        add_action('plugins_loaded', array($this, 'load_addons'));                        
        $this->allow_unfiltered_html(); 
        
//        $this->init_updater();
                
    }
    // end of __construct()

[Vladimir]

Did you try the “Admin menu blocking” add-on?

[Vladimir]

Hi Dave,

This is the WooCommerce code which creates the ‘customer’ role:

		// Customer role.
		add_role(
			'customer',
			'Customer',
			array(
				'read' => true,
			)
		);

As you see it contains the single ‘read’ user capability. Does your copy contains the same ‘read’ capability?

A possible problem would be related to other plugin or theme code and/or options which prevents login with role different than the ‘customer’. Try to deactivate all plugins and activate WordPress default 2021 theme. Will it change this? If Yes, then you can isolate a source of the problem activating plugins back one by one with a new login test.

[Vladimir]

I suppose it was a temporal networking issue. If you try to open this URL in a browser you will get the valid JSON data in response.

[Vladimir]

Hi Jon,

I reproduced the bug. Thanks for this report. I will work on the fix to include into the next update.

[Vladimir]

Check URE Pro settings, Add-ons tab:
if “Activate “Create” capability for posts/pages/custom post types” option is turned ON.
If Yes, then you have to grant to your role the ‘create_%’, capability for “USP Forms” custom post type. ‘%’ here is the custom post type ID.
“Add New” menu item is not available without ‘create_%’ capability if mentioned option is turned ON.

[Vladimir]

GraphQL plugin uses ‘manage_options’ user capability to protect all its admin menu items.

You can grant ‘manage_options’ to your role, then block unneeded menu items using Admin menu blocking add-on.

[Vladimir]

Hi,

This plugin uses ‘manage_options’ user capability to protect its menu/submenu items.

[Vladimir]

Hi,

If it’s applicable, send admin login credentials to support [at-sign] role-editor.com
I will look on the issue on site.

[Vladimir]

Read carefully the “Block not selected” part of the documentation article.

[Vladimir]

“Gravity Forms Add-Ons” section is provided by Gravity Forms itself via GFAddOn (includes/addon/class-gf-addon.php) class.
My test showed that this group is filled by caps as expected. I may suppose that some active add-on can break the data structures used for this. Try to deactivate temporary all GF addons and activate them back one by one with test repeated to check if this is true assumption and isolate a conflict.

[Vladimir]

Admin notification for 3: I don’t have a solution on hands. In theory custom code hooked to the post status change (e.g. transition_post_status) from ‘draft’ to ‘pending’ may resolve this task.

[Vladimir]

1, 2 – It’s possible to setup via “Edit restrictions add-on“. Activate it, then open “Edit post” dialog for a role and select “Own data only”.

3 – You had to use as a base role for the starting point the contributor role, not the author. Revoke from a role these capabilities: ‘publish_posts’, ‘publish_products’, ‘edit_published_posts’, ‘edit_published_products’, ‘delete_published_posts’, ‘delete_published_products’.

4. You can not control with URE what fields are shown at the front-end product page.

[Author]

Posts