Forum Replies Created
-
Posts
-
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.
Hi Guido,
Look, if ‘ure_manage_options’ capability was not accidentally granted to the user or his role.
Check if restrictions add-on is still active.
If you restrict front-end access view, user should not can edit the events.
Hello,
I don’t know plugins to recommend for this use case.
Look if you may use the URE Pro add-on, if it is suitable:
1) Content view restrictions – if company listing profile is a separate page and changes are made via front-end.
2) Posts/Pages edit restrictions – if company listing profile is a separate page and is edited via back-end at the page editor.
3) Other roles access add-on.If you can setup the list of user roles for your needs, user limited via “Other roles access” can grant only roles available for him and see users with this roles list only.
May be you can isolate what plugin or theme load its CSS globally and breaks a view at the URE’s page – just deactivate all plugins, activate WordPress 2021 theme, then test activating them back one by one.
Hi,
Do you have own suggestion for this fix?
If No, I need to look at the issue at the dev/stage copy of your site.There is no such setting in the URE plugin. Generally anyone can comment. Other depends from the comment system you use. Only post authors and editors can moderate comments.
