Got a fun bug for ya!<\/p>\n
Expected behavior<\/strong><\/p>\n Normally, when submitting an event through the Community Events form, you can add a new organizer as part of the process. If community event submissions are set to “pending” by default, then when the admin publishes the event, the new organizer is published at the same time. <\/p>\n Buggy behavior<\/strong><\/p>\n However, in Community Events 3.11, when submitting an event with multiple organizers, the new organizer is published ONLY WHEN the new organizer is the first one on the list of organizers for that event. When the first organizer is an existing organizer, and a new performer is added below it, the new performer doesn’t get published when the event is published.<\/p>\n Steps to reproduce the bug<\/strong><\/p>\n – Set default Community Event status to “pending”. By contrast, if you reverse the order in which organizers are added to the event, the new organizer IS published, as it should be:<\/p>\n – Fill out the community events form, using a new<\/strong> organizer. Below it, add an existing<\/strong> organizer as the second organizer. To reproduce the bug, you MUST make the first organizer(s) existing ones, and then add a new one below. You can do this all in a single submission process.<\/p>\n","protected":false},"template":"","class_list":["post-1008966","topic","type-topic","status-closed","hentry"],"yoast_head":"\n
\n– Fill out the community events form, using an existing<\/strong> organizer. Below it, add a new<\/strong> organizer as the second organizer.
\n– Submit the event.
\n– The event should be submitted successfully, and both the event and the new organizer are pending, as expected.
\n– Then go into the admin interface to review and publish the event.
\n– Notice that the event is published, but the new organizer is still pending<\/strong>. (You can see this by looking at the Organizers page, where it is tagged “pending,” and also by looking at the new organizer’s URL.)<\/p>\n
\n– Upon publication, the event and new organizer are both published, as expected.<\/p>\n