|
Maurice Langlais
|
April 7, 2015 at 12:16 pm
Hi, I was setting a user as Espresso Master Admin and noticed that I can get them access to all the functionality except being able to create new events and Edit existing events. Is this by design? Currently only the Administrator can create/edit events.
I tried selecting every capability belonging to Event Espresso in Role Editor for that role. They have access to everything but when clicking on an event to edit or when clicking on create new event only a blank screen appears.
|
|
Josh
|
April 7, 2015 at 1:23 pm
Hi Maurice,
Is this with using Event Espresso 3? If so, did you set the minimum page permissions for Event/Attendee Listings Page to Event Admin? There’s a screenshot of an example Minimum Page Permissions set up in the documentation:
https://eventespresso.com/wiki/roles-and-permissions-basic-add-on/#setup
|
|
Maurice Langlais
|
April 7, 2015 at 1:35 pm
No Josh, It’s EE4. I was just playing around with it and discovered that with the Espresso Master Admin given every ee_ capability, I also need edit_posts, and read and also manage_options. I don’t mind edit_posts and read because they need to have admin page access but the manage_options capability give them access to WordPress settings and other plugin and theme options that I wouldn’t want them to have access to. If I turn off manage_options all they get is a blank screen when they click on events under Events Espresso.
|
|
Josh
|
April 7, 2015 at 1:44 pm
Is that EE4.6 or is it lower (like 4.4 or lower?)
The Espresso Master Admin role is a throwback from EE3 and its Permissions add-on. Out of the box it shouldn’t have the capabilities that make it usable with EE4.
It will help to know how you ended up with an Espresso Master Admin role in the first place, and what method you used to configure the capabilities (ie which plugin are you using to modify the role’s capabilities?) Also, are you using any custom PHP code to override or filter default capabilities?
|
|
Maurice Langlais
|
April 7, 2015 at 2:03 pm
EE4.6 latest version. The site was migrated from EE3. I don’t have the permissions add-on from ee3 active. I assumed that the Espresso Master Admin was the role to be used to give others access to event editing, scanning, etc., since it still showed up as a role. I’m using User Role Editor plugin to configure the capabilities. No custom php code to override or filter default caps.
|
|
Maurice Langlais
|
April 8, 2015 at 5:56 am
I read through the documentation on EE4 capabilities. It does seem that a user needs to have the capability manage_options to read and edit events. I have created a user with these capabilities listed below. That user can see the Event Espresso menu item in WordPress admin as well as the Events and Venues menu items but clicking on any of those presents an error page 500 server error. If I add manage_options capability it all works.
This isn’t the best situation because that user can also edit WordPress settings as well as some settings for other plugins. I was wondering if this is how it is meant to work or if there is an error. Maybe I’m missing something?
edit_posts
read
ee_read_ee
ee_edit_event
ee_edit_events
ee_edit_others_events
ee_edit_published_events
ee_delete_event
ee_delete_others_events
ee_delete_private_events
ee_delete_published_events
ee_publish_events
ee_read_event
ee_read_events
ee_read_others_events
ee_read_private_events
ee_edit_venue
ee_edit_others_venues
ee_edit_private_venues
ee_edit_published_venues
ee_delete_venue
ee_delete_venues
ee_delete_other_venues
ee_delete_private_venues
ee_delete_published_venues
ee_publish_venues
ee_read_others_venues
ee_read_private_venues
ee_read_venue
ee_read_venues
|
|
Josh
|
April 8, 2015 at 7:12 am
Hi Maurice,
It should not be necessary to assign the manage_options capability to a user role in order to use EE4.6. Our documentation does not say that it’s a requirement as well.
Here’s a few things you can do to ensure the capabilities are set up correctly for the custom user role:
1) You log in as admin, and go to Event Espresso > Maintenance > Reset/Delete Data, then click “Reset Event Espresso Capabilities”.
2) Then you go to edit the user role (Users > User Editor Role > Select Role and change its capabilites). Then you type ee_ in the Quick filter input, click Select All, then click Update and confirm.
|
|
Maurice Langlais
|
April 8, 2015 at 7:48 am
Thanks Josh, I tried what you suggested twice. I get blank screen (500 server error) when clicking on anything in the tooltip menu for Event espresso except Barcode scanner, Help & Support, Extensions & Services. I also get the error when just clicking on Event Espresso in the sidebar. When I add manage_options everything works.
|
|
Josh
|
April 8, 2015 at 11:12 am
Hi Maurice,
There are a few possible conditions where manage_options would become the default required capability. It’s not something that Event Espresso 4 alone will switch to, but another plugin could have affect. Can you try removing the manage_options capability from the user role, then deactivate all plugins except for these two plugins:
Event Espresso 4 core
WP User Role Editor
Then try editing an event with the Espresso admin role. This will rule out whether or not another plugin is affecting the filtered capabilities.
|
|
Maurice Langlais
|
April 8, 2015 at 12:53 pm
Ok, you are right. There is a plugin issue or rather multiple plugin issues specifically these 2 that I need.
https://wordpress.org/plugins/types/
http://www.woothemes.com/products/wooslider/
these 2 I can probably do without. The woothemes helper is just for updating woo plugins and themes I can do that manually and the importer I don’t need activated.
https://wordpress.org/plugins/wordpress-importer/
woothemes helper
|
|
Josh
|
April 8, 2015 at 1:21 pm
Hi Maurice,
I’ve got the Types plugin loaded up locally and I’m not seeing any issues with using custom user roles that have Event Espresso capabilities. Can you check to see if there are any errors in the PHP logs from when you tried to load the Add New Event page using the custom user role?
|
|
Maurice Langlais
|
April 9, 2015 at 8:42 am
Josh, I think this has turned out to be a memory issue and not related to any specific plugins. It seems odd that manage_options capability “fixes” it. Anyway, I think we can say this has been resolved for now. Thanks for all your help.
|
