|
cjcm796
|
November 22, 2016 at 10:46 am
Hi,
1. I installed the EE Event Roles Plugin that creates the ‘Event Organiser’ and ‘Events Maneger’ roles for use within Event Espresso.
2. A new user is created with the Event Organizer role.
3. When adding a new event, I got the following error messages:
Notice: Undefined index: default_user_create_role in D:\Wordpress\www.myuniversityevents.dev\wp-content\plugins\eea-wp-user-integration\EED_WP_Users_Admin.module.php on line 753
Warning: Cannot modify header information – headers already sent by (output started at D:\Wordpress\www.myuniversityevents.dev\wp-content\plugins\eea-wp-user-integration\EED_WP_Users_Admin.module.php:753) in D:\Wordpress\www.myuniversityevents.dev\wp-includes\pluggable.php on line 1174
The following have been observed:
1. The new event has been successfully added despite the above error messages
2. Enabling the “manage_options” under Edit Capabilities: General for this Event Organizer role seems to work fine without this error, however this is not desirable as I do not want to let Event Editor role to have this capability to “manage_options”.
Hope to get feedback ASAP from EE support team.
Thank you in advance.
|
|
cjcm796
|
November 22, 2016 at 10:50 am
Additional Information, the site is currently under development using local web server by ServerPress (free version) which is based on Xampp. Hope this helps.
|
|
Tony
|
November 22, 2016 at 10:59 am
Hi there,
Thank you for the detailed report.
We have a fix for this in the next version of the EE4 User integration add-on which will be released soon.
The problem is the default_user_create_role option has been removed for non-admin users but the code to save the option is not checking if the user is an admin and attempts to access the value.
When WP_Debug is enabled (or display_errors is enabled on the server) this then throws a notice on the site which then causes the ‘headers already sent’ error. As it is only a notice for a setting that does not apply directly to the event it does not cause problems other than throwing the notice itself.
On a production site with WP_Debug disabled this won’t cause any issues (as the notice will not be thrown which means the headers already sent error will not be either) but we’ll get this released asap.
|
|
cjcm796
|
November 22, 2016 at 11:19 am
Thank you Tony for quick reply.
Just wondering when is roughly the fix will be released?
TQ.
|
|
Josh
|
November 23, 2016 at 9:35 am
Before 2017.
|
