Forum Replies Created
-
Posts
-
In order to exclude product from listings, you have to select action “404 HTTP error”. Content view restrictions protects directly only post/page content or full description for the products. It does not prohibit to theme or plugin to show any other product attributes, like price, image, etc. until you select the “404” or “redirect” action.
Take into account that you can set view restrictions directly for the product category.
Hi,
‘Easy WP SMTP’ plugin checks ‘manage_options’ capability in 2 places:
1) when adds own settings page under the “Settings” menu;
2) when add a couple of internal hooks for the wp_admin.It does not send email messages itself. It just allows messages sent by WordPress itself to be sent via external mail server (SMTP).
You need to check why in some cases email is not built by WordPress itself or responsible plugin.
Re-check that user can at least the ‘list_users’ capability.
If you have “Admin menu access” add-on active, check if “Users” menu is not blocked for role granted to this user.
Check if some other plugin does not block “Users” menu for this user or his role.Hi,
Elementor protects its menu items including the “Settings” one with ‘manage_options’ user capability.
Take into account that after granting ‘manage_options’ to the ‘editor’ role it will get access to a lot of other critical menu items, like general WordPress “Settings”. You may use “Admin menu access” add-on to block them for editor role.Clarify, what plugin settings do you try to access?
What user account do you use for that, admin? If not, tell about user permissions and restrictions applied to that user.Hi,
Excuse for so huge delay with response. Yes, it will work. ‘no_role’ seems more nice for me. I will provide access to the beta for testing until the end of November, 2021.
The same result. If you can repeat this at the development copy of the site it would be good to get admin access to investigate the issue. If it’s possible send credentials to the support email address.
Unfortunately, I can not repeat this at my test environment. If it’s possible to look at the issue on site (dev. copy preferred), send credentials to the support [at-sign] role-editor.com
Hi Guido,
Look at the Settings->User Role Editor->Additional Moduls tab, if related checkbox is turned ON. Yes, you may send login credentials to support [at-sign] role-editor.com with description/example who and what should see, but what should not see.
Hi,
URE will ot help. URE is responsible for the WordPress access settings. Direct file access is not managed by WordPress. It’s managed via HTTP server software: Apache or Nginx.
Hi,
I confirm that currently role=”none” works for the not logged-in users only – traditionally, from very begin.
From one side, registered user without role can easily get access to the content with roles=”none”, it’s enough just logout. But, many sites use this shortcode to show content for not logged-in users only, to invite to login, for example. It will be not correct to show such content for logged-in users, which does not have role at the site. Backward compatibility is very important.What if to add something like ‘none_for_logged_in’, which will work especially for logged-in users, which does not have role for this site? Finally, it will be possible to user shortcode with parameters like roles=”none none_for_logged_in” especially for your case.
