Community Events: reverts to system Default Organizer on Edit (Possible bug?)

[Abigail Marshall]

A user has reported that in Community Events, when going back to enter a previously-entered event, the system reverts to the default organizer. I think I have resolved this on our site by simply changing settings so that there are no defaults for organizer or venue. However, I wanted to report this if it is unintended behavior. I would assume that a default would show up on event creation, but I would not expect to see it with an edit to an event where another organizer had already been sent.

[Josh]

Hey Abigail,

Thanks for reaching out to us!

To clarify, after a user has successfully submitted an event and they go in to edit that event on the front-end of the site the Organizer doesn’t reflect the previously selected and applied organizer for the event within the dropdown but shows the organizer from the default organizer setting?

Thanks!

[Abigail Marshall]

I’ve replicated the error. Now that I no longer have a “default” Organizer set, here is what happens.

If I go to the edit menu on the front end, to edit an even that already has an organizer entered, when the edit screen comes up there is no Organizer shown as set. I just see the drop down menu as it would appear for the initial event entry.

If I save, then the initial organizer setting is lost — so it is not a matter of a display problem. The user would have to re-select the organizer prior to saving after an edit.

So yes, it is a bug –and eliminating the default setting is not a solution.

[Josh]

Hey Abigail,

I’ve done some further testing on this as well and can also verify the bug here.

I’ve created an internal bug ticket for tracking this issue. I’ve added this thread to that ticket and you’ll be notified here as we make progress on this one.

If you have any further questions about this or the process, please don’t hesitate to follow up here.

Thanks!

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Leah]

Hello,

Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.

Best,
Leah

[Geoff]

Hey Abigail,

Just wanted to follow up and let you know that we released version 4.1.1 last night and it included a fix for this issue. Please update to the latest version if you haven’t already and do let us know if you continue to see any issues from there. 🙂

Cheers and thanks for your patience while we worked on this!

Geoff

[Author]

Posts