Forum Replies Created
-
AuthorPosts
-
Vladimir
KeymasterClarify, what URE Pro add-ons do you use:
– Did you set content view restrictions for pages?
– Did you set restrictions for front-end menu?Vladimir
KeymasterHi,
You need to revoke ‘edit_products’ capability from a role in order user with that role does not see “Products” admin menu item. Did you?
Vladimir
KeymasterHi,
Good that you found a workaround.
I can not repeat the described issue though. Can you record a short video with the steps which I should do to repeat it?Vladimir
KeymasterI wrote a special module for exporting all user roles to CSV file.
You can get it from this link.
Read comments at file header as a short instruction.
I will integrate this code with User Role Editor Pro little bit later.Vladimir
KeymasterHi Ismael,
Currently export of roles to CSV is not available at URE Pro.
I may add this feature if you will wait few days.Vladimir
KeymasterHi Alex,
Select “Return HTTP 404 error” action instead of “Access error message” one. It will exclude post from all listings.
Vladimir
KeymasterI forgot to mention that URE grants its own user capabilities (started from ‘ure_’) automatically to the ‘administrator’ role only. It’s happened on plugin activation. If user has another role, then ‘ure_’ capabilities should be granted to that role before it will see URE in admin menu.
Vladimir
KeymasterDoes your user (with superadmin privileges) has ‘administrator’ role?
URE hides itself from other users with access to plugins list.URE may not add menu “Users->User Role Editor” as ‘administrator’ role does not get URE’s specific permissions during plugin activation. “Deactivate/Activate back” helps usually in such rare situation.
You may make another try. Delete
plugins/user-role-editor-pro
folder via FTP. Open plugins list – WordPress will deactivate unexisted plugin automatically. Then try to install and activate URE Pro again.Vladimir
KeymasterIs it WP multisite?
Do you write about “Network Admin->Plugins”?Vladimir
KeymasterThanks for the help with testing and suggestion. I will realized it, with time…
Vladimir
KeymasterTry beta version 4.49.4.b1 which contains a fix for the described issue.
It’s available from Downloads page after login.Vladimir
KeymasterThank you for clarification. I apologize for the misunderstanding.
I reproduced the issue. It’s a bug. Thanks for discovering. I will investigate it and develop the fix.
Vladimir
KeymasterI thought you specially try to restrict view of the forum topic and its replies with URE Pro “Content view restrictions” add-on. Is it wrong?
While you don’t set view restrictions at the topic editor “Content View Restrictions” meta box, this forum topic visibility is not restricted by URE Pro. It’s managed by bbPress user capabilities only.
Do you have a problem with all topics or with just the selected subset?
If the 2nd, check what option is set at “Content View Restrictions” meta box for that topic. In order URE Pro “Content View Restrictions” does not manage view of the topic you need to select “Allow->All visitors” or “Selected roles ->empty list of roles”.Is not restricted topic visible when you turn OFF “Activate content view restrictions” checkbox at “Settings->User Role Editor->Additional Modules” tab?
Vladimir
KeymasterIt’s the 1st time when someone tries to use “Content view restrictions” settings for the bbPress forums. Thanks for showing the issue which it raises. It seems I have to exclude bbPress’s custom post types (forum, topic, reply) from the “Content view restrictions” add-on scope.
“Content view restrictions” add-on is developed for the existing content: posts, pages, custom post types. That is for item, which is published from the back-end and authorized persons defines for it the view permissions.
Replies/answers is sent to forum topic from front-end by ordinal users, which are not authorized to set view permissions for their posts.
So “reply” custom post type item is published with default permissions – visible to all.If you restricted view for topic, it’s visibility for not authorized user depends from the selected access error action:
– topic is fully hidden from the topics list if “404” was selected,
and
– topic title is shown for all if “error message” was selected, even if user does not have permission to view this topic.Restriction applies just to this topic custom post type item content (description), and does not apply to any reply/answer sent to this topic, as ‘reply’ is another custom post type created by bbPress and every item may/should have own view permissions – which may be set directly at the reply backend editor.
Sorry for the long and possibly not too clear explanation, but finally I do not recommend to use “Content view restrictions” add-on for bbPress topics and replies. It’s not suitable for this purpose.
View restrictions for bbPress forums and topics requires a special solution.
Let me know if you are interested for custom solution which would restrict view of forum and/or topic by the user role. I may write it for testing with your help as the base for the future add-on for User Role Editor Pro.
Vladimir
KeymasterHi,
Let me test this. Show plugin download link if it’s free or share its .zip via DropBox or GoogleDrive. I use paid product received from client for the testing purpose only.
-
AuthorPosts