[Vladimir]

“Show access error message” option does not exclude post or product from the listings, it just hides its description. So when not authorized visitor opens such post he sees its title but sees access error message instead of post content – instead of product full description in case of a WooCommerce product.

In order to fully hide product/exclude it from all listings you have to select one of “Return HTTP 404 error” or “Redirect to URL” options.

[Vladimir]

Did you have a chance to test version 4.41? One of users reported PHP fatal error “Call to undefined function et_builder_register_layouts()”, while this code works fine at my test site with Divi 3.0.98.

[Vladimir]

Do you use “Admin menu access” add-on to block some other CPTs or ‘Posts’ menu from this user? If Yes, show me a screenshot from “Admin menu” for this role.

[Vladimir]

Hi,

This plugin menu item “Tools->Send email” is protected by ‘manage_options’ capability. So you have to add this capability to ‘editor’ role and then block unneeded menu items using “Admin menu access” add-on.

[Vladimir]

Hi,

Try to temporally switch Off this option “Force custom post types to use their own capabilities” at the “Settings->User Role Editor” and re-test “Users->User Role Editor”. If it will help, then the error from screenshot is related. This fatal PHP error requires a fix any way though.

What version of Divi do you use? I tested URE Pro with 3.0.98.

[Vladimir]

Hi Kevin,

Check a browser JavaScript console (Shift+Ctrl+J in Google Chrome) for error messages. I suppose a conflict with some plugin which prevent JavaScript code to work correctly.

[Vladimir]

Hi,

It’s not possible inside URE Pro. You have to use PHP code to make this update. Like this:

add_action('admin_init', 'ure_content_view_add_role');

function ure_content_view_add_role() {
    global $wpdb;
    
    $key = URE_Content_View_Restrictions::content_for_roles;
    $query = "SELECT meta_id
                FROM {$wpdb->postmeta}
                WHERE meta_key='{$key}' AND meta_value='level1'";
    $list = $wpdb->get_col($query);
    if (empty($list)) {
        return;
    }
    foreach ($list as $meta_id) {
        $query = "UPDATE {$wpdb->postmeta} SET meta_value='level1, level2' WHERE meta_id={$meta_id} LIMIT 1";
        $wpdb->query($query);
    }
        
}

This code takes all posts and pages for which content view access roles set to ‘level1’ and replaces ‘level1’ with the list of roles: ‘level1, level2’.

1. Create a fresh database backup
2. Place this code as a separate .php file into wp-content/mu-plugin/ folder as a Must Use plugin.
3. Open any page under yoursite/wp-admin
4. Remove this .php file from wp-content/mu-plugin/ folder.
5. Check the results.

Code will be more complex if you need to make changes for the pages only and do not touch any posts which can have the same role in view permissions.

[Vladimir]

Hi,

Thanks for this report.

Yes, this piece of code is needed to provide access to custom post type ‘et_pb_layout’ user capabilities at User Role Editor page when we force it to use own capabilities (‘edit_et_pb_layouts’, etc.) instead of ‘post’ like.

It seems that it stopped working after of some Divi theme update. I changed line

require ET_BUILDER_DIR . ‘layouts.php’;

to

et_builder_register_layouts();

This change will be available with upcoming version 4.41

[Vladimir]

Thanks for letting me know.

[Vladimir]

Hi Aldo,

Edit restrictions add-on support hierarchy for the WordPress built-in pages only. It applies edit restrictions from the parent page to all child pages by default.

I did not meet with usage hierarchical CPT until this moment.

A possible workaround – use categories as working groups. User restricted by category can post to that category only. A problem – parent post will not be assigned automatically.
URE Pro does not restrict parent posts available to a user.

It seems that URE Pro is not ready for hierarchical scheme realized by you.

May be you will think about work with this CPT without hierarchy, separating access to the items inside this CPT just by categories?

[Vladimir]

Can you share Beaver Builder Pro copy for testing?

[Vladimir]

Hi,

This feature is not realized yet. Thanks for adding +1 to a quantity of clients who desire this option. It will do it with the next update.

[Vladimir]

Developer who added custom post types at your site registered theme with user capabilities default for the WordPress built-in posts, but protected admin menu items by ‘edit_pages’ capability.
I used “Admin menu access” add-on to get this information: https://www.role-editor.com/block-admin-menu-items

Then I added ‘edit_pages’ capability to the ‘Speaker’ role and blocked unneded menu items with the same “Admin menu” button.

Tests showed that while custom post types are defined with default ‘post’ capability type, they require really capabilities from the ‘pages’ group. So I added them to the ‘Speaker” role.

[Vladimir]

You can send URL and admin credentials to support [at-sign] role-editor.com
To what custom post type do you wish to provide access and to what role?

[Vladimir]

Hi,

Do you use “Admin menu access” add-on from User Role Editor Pro and blocked some menu items for this role?

A lot of User Role Editor Pro users work with AVADA theme and do not report any problem.

In general if you just added a capability to a role, the rest work makes WordPress itself and theme and/or plugins which check user role and capabilities. So if a problem is raised really for this reason you can ask support question to fusion-builder plugin developers too.

I can investigate the issue in my test environment if you provide me access to the database and site files copy – via DropBox or GoogleDrive (support [at-sign] role-editor.com)

[Author]

Posts