[Vladimir]

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.

[Vladimir]

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.

[Vladimir]

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.

[Vladimir]

Hi,

Use this custom filter to change the restriction:

ure_attachments_show_full_list

[Vladimir]

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.

[Vladimir]

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.

[Vladimir]

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.

[Vladimir]

Hi Janneke,

URE does not restrict user with ‘administrator’ role in any manner. Thus you can not select ‘administrator’ role for restriction at any add-on.

You may use a copy of administrator role for the selected users, which it’s possible to restrict.

[Vladimir]

Hi Erik,

I updated the code to fix the issue. Take a look.

[Vladimir]

I suppose, that plugin responsible for the front-end access to the downloads checks not user capability, but user role. If this plugin has settings for the list of role, allowed to download, add ‘administrator’ to that roles list.

[Vladimir]

Hi,

Thanks a lot for pointing to this bug. It’s a typo. Quick fix: open post-edit-access-role.php file for editing and replace plus ‘+’ character with this the dot: ‘.’
Correct version of line #72:

return array('result'=>'success', 'message'=>'Posts edit permissions for role:'. $role_id, 'html'=>$html);

I included this fix to the next release.

[Vladimir]

Hi Erik,

You are right. To make it universal use right version of the query with “IN ($ag)”, which currently is commented out by /* … */. Hardcoded ‘SBU004’ may stay there from the testing/debugging stage.

[Vladimir]

Hi,

Sorry for the delay. Let’s wait for the end of month. I will try to add this feature to the next update I plan to publish at the end of October – begin of November 2021.

[Vladimir]

Hi,

Additional authentication parameters are required for the API calls. This post may help

Authentication

[Vladimir]

URE does not include suitable hooks to rename plugin. FYI, I do not appreciate this.

Yes, if you will replace plugin name directly in the plugin source code, the changes will be overwritten every time you will install updated version.

[Author]

Posts