|
KBrownlee
|
February 15, 2025 at 3:44 am
We recently upgraded to EE5. We have a dedicated WP role for event management which has been granted all the EE capabilities related to Events and several related to Venues.
Users with this role are not able to see the Venue Details or Available Tickets sections when editing an Event. Administrators are able to see these sections properly. What might we be missing?
|
|
Garth
|
February 17, 2025 at 11:49 am
Hi there,
When you edit that role, do you see the additional Event Espresso capabilities to grant that user?
For example, you will see capabilities that begin with ee_, so ee_edit_venue and ee_read_venue, ee_read_venues,ee_read_others_venues`, etc.
You may need to update your role to include those additional capabilities.
|
|
KBrownlee
|
February 17, 2025 at 3:12 pm
The role currently has the following EE capabilities assigned:
* ee_edit_events
* ee_edit_others_events
* ee_delete_events
* ee_publish_events
* ee_read_private_events
* ee_delete_private_events
* ee_delete_published_events
* ee_delete_others_events
* ee_edit_private_events
* ee_edit_published_events
* ee_edit_venues
* ee_edit_others_venues
* ee_publish_venues
* ee_read_private_venues
* ee_edit_private_venues
* ee_edit_published_venues
There do not appear to be any permissions explicitly related to tickets.
|
|
Garth
|
February 17, 2025 at 3:39 pm
My ee_events_administrator role has 154 individual permissions, while my Administrator role has 272 individual permissions.
There are separate capabilities for reading, editing and deleting and sometimes publishing. Double check your read capabilities, e.g.: ee_read_event, ee_read_events, notice the singular and plural form. The singular form of a permission is used to for access to their own events/venues/etc, while the plural form is access to other’s.
WordPress permissions can vary depending on the plugins installed. You can start by granting the user nearly full access, then remove permissions as needed, or add access gradually by assigning permissions one by one. Either approach involves some trial and error through a process of elimination and checking.
This spreadsheet helps define many of the capabilities in Event Espresso: https://docs.google.com/spreadsheets/d/1paQ8gdiZmIpOTJetRtk0_7GZfsWIXkioqrWmXxS4FZo/edit?gid=1#gid=1
|
|
KBrownlee
|
February 18, 2025 at 2:59 am
Thanks for sharing the spreadsheet, I had no idea how many permissions were in use, nor that EE relied on core WordPress permissions in addition to the EE-specific set.
We are using the Member plugin from MemberPress to expose Role editing. Based on your prompting, I checked the Custom heading and discovered another 50 or so EE-specific permissions. However, absolutely all of these are already granted to our event management role.
I don’t particularly want to grant more permissions to our event coordinator and then reduce their set via trial and error, at least not if I can avoid it, since we’re talking about a difference of some 200-odd permissions.
Other than the ability to edit default tickets, I did not see anything related to tickets in the spreadsheet. What else can / should I look for to narrow this down?
|
|
Tony
|
February 18, 2025 at 11:01 am
Hi there,
I have a plugin with 2 roles in giving an example of this here:
https://monosnap.com/file/OByG22pbZaAHZZNz6LXThha9GutLux
In that zip you’ll find 2 roles, an Events Administrator (which has full access to Event Espresso) and an Event Manager role (which has access to events the account is assigned as the author to).
Take a look at the capabilities assigned to that role and compare those to yours, that should help identify what is missing here.
|
|
KBrownlee
|
February 18, 2025 at 5:12 pm
Thank you guys so much for the support. I’ve investigated this further and discovered the problem was confined to a single user – when I assign the role to another user, they can edit the venue and tickets correctly. This case can be closed, apologies for the distraction.
|
|
Garth
|
February 19, 2025 at 4:44 pm
Glad you figured it out.
|
