[Vladimir]

Is it possible to look on your site admin on-line? If ‘Yes’, send login credentials to support [at-sign] role-editor.com.

[Vladimir]

Yes, it is safe to delete free version at ‘user-role-editor’ folder after installing and activating of Pro version at ‘user-role-edito-pro’ folder, but only directly, via FTP. If you delete free version via WordPress you will lose the settings you made for URE. Both versions use the same storage for plugin settings.

[Vladimir]

Hi,

Do other buttons work? Check browser JavaScript console for the error messages. Show a screenshot with them if you find any.

[Vladimir]

1) There is now way to manage this by custom post type ID. You should input the ID of the posts of those types which you wish to restrict access to. You may see the post ID at the browser address line when you open that post for the editing.
To restrict access to other post types use:
a) is post type uses its own capabilities set like ‘edit_events’, exclude ‘create_events’ capability from a user role;
b) if post type uses the same ‘edit_posts’ capability use ‘admin access blocking’ add-on: https://www.role-editor.com/block-admin-menu-items

2) Currently only the list of posts, pages ID is supported. I think about to add automatic support for the child pages as it is not the 1st feature request. But it is not realized yet.

[Vladimir]

Thank you. I updated plugin metadata at the update server.

[Vladimir]

Create file wc-settings-remove-tab.php at the wp-content/mu-plugins folder and insert to it this code:

<?php

add_filter( 'woocommerce_settings_tabs_array', 'remove_webhooks', 25);

function remove_webhooks($pages) {

  if (current_user_can('wc_manager_restricted')) {
    unset($pages['webhooks']);
  }

  return $pages;

}

Replace wc_manager_restricted with your role name or capability.

[Vladimir]

Add to the role or user these capabilities:
‘search_regex_read’ – it gives access to the “Tools->Search Regex” menu,
‘search_regex_write’ – it allows to modify WordPress data.

[Vladimir]

Hi,

Thanks for the good feedback.

Post edit restrictions by categories was added to the development version 4.19.b. It is available at download page.
Post view restrictions by categories is under development currently.

If WECRB plugin realized events as the custom post type veiw/edit restrictions by categories should work for events then.

It will be useful to get mentioned WECRB plugin for testing. If it’s applicable, send the installation package to support [at-sign] role-editor.com. It will be used for the testing purpose only at my local development environment.

[Vladimir]

Hi,

Yes, you really can send screenshots to support [at-sign] role-editor.com

What is a real problem? According to screenshots You allowed to edit the only page and that user have access to that only page, right?
If you don’t need that user may create new posts/pages revoke create_posts, create_pages capabilities from him.

[Vladimir]

I tried to repeat a described issue, but without success. Posts are shown at the post edit page with pages included to the gallery only as for editor, as for later assigned admin-copy role.
In case you will meet a similar issue again, let me access to the site to take a look in order to try to repeat it at my development environment.

[Vladimir]

Hi Carolyn,

Thanks for the feedback.

[Vladimir]

Thanks for the valuable information.
I had no chance to test it yet. But I really will do it these days.

[Vladimir]

Edit access to the pages is realized at the users level currently. If user can edit pages you may restrict him to edit just the pages from the ID list. Follow this post:
https://www.role-editor.com/allow-user-edit-selected-posts/

If you talk about access to the plugin’s menu, use “Admin menu access” add-on, as described at this post:
https://www.role-editor.com/block-admin-menu-items

[Vladimir]

I can not repeat. Please send to support [at-sign] role-editor.com the screenshots of your URE plugin settings, and what part of “Gravity Forms Stick List” dissappears.

[Vladimir]

Hi Carolyn,

The issue with blocking direct access to the customize.php link was fixed with version 4.18.3. Please update and test.

[Author]

Posts