|
info@bhaa.ie
|
December 7, 2018 at 1:25 pm
Hi,
Is is possible that the ‘Ticket Capability Requirement’ could support two groups. All the documentation seems to indicate that only 1 group is currently supported.
In our case, we have had a ‘Membership 2018’ group, and we will setup a new ‘Membership 2019’ group. For January, we have this special case, where members from 2018 or new members from 2019 should both get the discount on the same ticket. This allows 2018 members renew their membership during January.
Regards,
Paul
|
|
Josh
|
December 7, 2018 at 1:33 pm
Hi Paul,
Yes, because the groups can share a common capability.
For example, a WordPress “admin” role will have a ‘edit post’ capability, and so will a WordPress “editor” role. They both share that edit_post capability.
WordPress also allows for adding new, custom, capabilities. So for your example, you could create a capability, name it something to the effect of
late_2018_early_2019. The name isn’t important as long as it’s unique, and makes sense for your purposes. Then you assign that capability to both “Membership 2018” and “Membership 2019” roles.
Some membership plugins, like Members, have a built-in capability editor.
|
|
info@bhaa.ie
|
December 7, 2018 at 1:45 pm
Great and thanks for the quick reply. I think it might be worth expanding on the text in the help guide in the Ticket Capability section, since a simple example like you gave above would help clarify thinks for the users.
|
