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 R&P Pro vs Promo Codes | Event Espresso - Staging Server
I’m trying to understand the relationships between Event Manager and the Promo Codes.
If an Event Manager wants to create a Promo Code then I must give them access to the Promotional Codes page via the User Permissions settings page. This level of access allows any Event Manager to edit/delete other user’s coupon codes (which is bad).
Shouldn’t the Event Manager be able to create their own Promo Codes without the ability to edit/delete other users’ codes. The Event Manager can even edit the Site Admin’s promocodes.
I have to provide Permissions to the Event Manager to allow them to create/select their own Promos. Is this correct?
After giving the Event Manager role Permission to the Manage Promo page:
– They can appear to edit anyone’s Promo, but generate an error when attempting to update. Is this intended?
– They can delete others Promos freely. This doesn’t seem intended.
That’s my investigation, I feel like there’s an error here someplace.
At this time Promo codes are shared, rather than restricted. I will certainly add a +1 to the feature request for allowing Event Managers to only have their own promo codes.
I have noted down that error and made a ticket for it. It seems to only appear if the promo code is updated when no changes have been made, regardless of user.
Viewing 2 reply threads
The support post ‘R&P Pro vs Promo Codes’ 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.