Currently, for fieldsets and containers you can set create, view, and edit permissions for the element and all of its children elements. I would love to see this exact same functionality applied to Wizard Pages.
Use case:
I am currently building an employment application form. We want a to add a page for the Human Resources Department that contains fields about race, gender etc. We want the ability to restrict access to this page to only the person applying, and those with a special "Human Resources" role.
This can be implemented using fieldsets for the time being, but it is a little clumsy, because I have to stick it on a an existing wizard page, where it doesn't really make sense.
Comment | File | Size | Author |
---|---|---|---|
#12 | restrict_wizard_page-2902631-12.patch | 50.59 KB | jrockowitz |
| |||
#9 | restrict_wizard_page-2902631-9.patch | 49.46 KB | jrockowitz |
#4 | restrict_wizard_page-2902631-3.patch | 16.39 KB | jrockowitz |
Comments
Comment #2
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commentedThat is an awesome concept/feature.
It is going to require some very minor refactoring and test coverage.
Comment #4
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commentedComment #5
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commented@ebren Most of the patches are going to be for testing the needed refactoring to get this to work.
Comment #9
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commentedComment #12
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commentedComment #14
jrockowitz CreditAttribution: jrockowitz at The Big Blue House commentedAll the tests are passing and I need to start working on a related issue in a new ticket, so I committed the patch. Please download the latest dev release to review.