Using AAC to lock certain pages for certain roles
This is what I want to accomplice:
I want to use a custom-post-type to create portfolio items
Then I want to make a page which loads the content-type (portfolio).
How to “lock” the page for my client so he/she can not delete/undo the loopbuddy part.
I would like to give the client the opportunity to create and edit pages, but the “portfolio-page” he should not edit.
The client will make portfolio items in the back-end and they will appear on the destined page.
How can I use advanced access manager to create a this?
How to give a role rights to pages except the portfolio-page?
Thanks for your time and help
- The topic ‘Using AAC to lock certain pages for certain roles’ is closed to new replies.