Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Wordpress role level access to EE backend | Event Espresso - Staging Server
I’m sure this is covered somewhere, but I couldn’t find it in a search just now. Can you set which wordpress user roles (Author, Editor, etc) are allowed to access event espresso backend functionality, if so, where do you do that. If not, what roles have access to EE by default? (we have a need for someone to have access to create/modify events, but only Author level on the rest of the website.
Also if not, then I have a more detailed WordPress question: is the EE administration a wordpress capability, so I can create a new custom role with that turned on {using something like Capability Manager Plugin or Members Plugin which allow me to create custom roles}. If it’s not a specifically created capability, what capabilities would I need to turn on in my custom created role to give someone EE access?
A follow up on this: where do we set the permissions for the EE functions explained below from your link?
“Then assign this new user role the permissions, or access to Event Espresso features, that this role should have. As an example, if the events that the event admin will be publishing will offer discount codes, set the ‘Discounts Page’ permission to be available for the event admin. Be sure to save when finished.”
You’ll need to update to a more recent version of Event Espresso in order to use the roles and permissions add-on. We’ve put together a guide on how to manually update Event Espresso here:
The support post ‘WordPress role level access to EE backend’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.