Home›Topic Tag: Controlling access to content editing
Topic Tag: Controlling access to content editing
Access plugin allows you to control access to content editing for different users. You can set access rules for entire user types or for specific users.
When you ask for help or report issues, make sure to tell us on which content and user types you are trying to apply access control.
Viewing 15 topics - 181 through 195 (of 218 total)
1) Edit the page "Registrazione NCC", section "Post Group", choose option as :
No Post Group selected.
2) Dashboard-> Toolset-> Access Control-> CRED form
in section "CRED Users Frontend Access",
find "Create Custom User with CRED Form "Registrazione NCC"", enable option for guest user.
Problem: I would like to allow Access WPML groups to edit specific posts in other languages.
Solution: Hi, at this time Access does not offer the ability to specify read/write permissions per language, per User, per post or per CPT. To achieve that type of granular control, you might be able to use inline Access Controls or Conditional HTML code on the front-end of your site to restrict access to specific parts of your site content, like individual CRED forms or specific post custom fields. However, enforcing those access rules on the backend isn't possible with the current software. That would require a custom code solution.
Problem:
What are the options for displaying different content to different users on the front-end?
Solution:
To display different content on the front-end according to some criteria you essentially have two options.
If the thing being tested relates to the person doing the looking (the user browsing the website is registered and has a certain role because they have paid for a particular membership, for example) then you can use Access to restrict the visibility of whole pages, or to selectively show certain content on a page (as described here: https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/).
If the thing being tested relates to the thing being looked at then you would need to add custom fields to the content being viewed and then use the wpv-conditional shortcodes to test the content of those custom fields and selectively display what is wrapped in the shortcode, as described here: https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
Problem:
A user with a role of Editor is unable to edit custom posts with WPML, only the administrator can.
Solution:
In WPML > Translation Management > Multilingual Content Setup the first option is to Create translations manually or Use the translation editor.
If you select 1 then you can use Access to set the ability of different roles to edit translations.
If you select 2 then you *must* create a translator within WPML and assign translation jobs to them.
Problem: I would like to add a registration form that allows people to claim ownership of a post. Once an admin approves their ownership, the registrant becomes author of that post.
Solution:
If I were trying to do something like this, I would follow this process:
- Create a new CPT called Pending Approvals
- Add custom fields to the Pending Approval CPT - user ID, university ID, college ID, and school ID
- Use cred_save_data to create a Pending Approval post whenever someone submits the User Registration form while trying to claim ownership of a University, College or School.
- Save the new User's ID and the appropriate University, College or School ID in the Pending Approval post
- Create a View of Pending Approval posts. In the Loop of results, include a "Delete Post" link that can be used to decline the ownership request. Also include an Edit CRED form that edits the University, College, or School. Hide or remove all the visible inputs from this form except the submit button, and give it a name like "Approve Ownership"
- Use the cred_save_data hook to update the University, College, or School post author when this form is submitted, and trash the Pending Approval post.
- Insert the View of Pending Approval posts in a page that is restricted to site administrators.
