When admins edit events, member who posted it loses control

Product Support

AI-generated summary

The discussion revolves around a potential bug where, when an admin edits a community member’s event, the original creator loses control of the event. Ryan_Scott reports this issue, noting that even after an admin makes changes, the original member can no longer edit or manage the event. tobiaseigen moves the post to a dedicated topic for investigation and acknowledges it as a possible bug. The admin attempts to reproduce the issue but is unable to do so, asking for more details. tobiaseigen follows up, requesting steps to reproduce the problem if it persists.

1

I wish when I edited a community member’s event as admin (the time for example, then hit save), that original member could still have control of that event after

Said another way, if for various reasons I have to edit a calendar event as admin, the original creator of the event loses ‘control’/ownership to then be able to edit that event they originally created

also same if I create an event and impersonate someone. That person who is impersonated is not able to there after control/edit the event (even though they “own” it)

this discourse: https://awg.osdr.space/about

2

Hi Ryan! I moved your post into its own topic so it can be investigated. That does sound like a bug to me as you describe it. If this is an urgent issue you need an answer on, as a customer you can also reach out to our team by email.

That’s an interesting site! You might like to add it to the What are your favorite Discourse sites in the wild? topic.

3

I just tested this and am not able to reproduce the issue you are describing. Here is what I did:

  1. create test user
  2. as test user, create new topic containing an event
  3. as admin, look at the topic and edit the event using the […] button then → Edit event. make a change, save changes.
  4. refresh browser - test user is still owner and able to edit.
4

@Ryan_Scott were you able to figure this out? If not, please provide steps to reproduce the problem and we can determine if this is a bug. If there is no problem then I’d like to delete this topic.