Problem/Motivation

As an organizer of an event that has more than one organizer:

  • One organizer creates the event node
  • Thereafter, only that organizer can modify the event node

This make organizing events unnecessarily difficult, contributes to organizer burnout (the burden is placed on one person to maintain the event node), and slows down changes to event information (need to wait for the only person allowed to make the update to make the update).

Proposed resolution

Provide a way for the event node author to grant edit access to the node. For example, add a user reference field whose referenced users can edit the node.

Comments

jdleonard created an issue. See original summary.

volkswagenchick’s picture

I don't have a solution as to how to implement this, but would love the maybe have all organizers have edit access to add sponsors, speakers, CoC contacts, etc

grienauer’s picture

this would help a lot.
I would like to go easy with that, and the funn node could be editable.
So it could be a "simple" rule, where all Organizers of the event hav also Edit rights of that node/event!

drumm’s picture

Version: 7.x-3.x-dev » 1.0.x-dev
Status: Active » Postponed

We’ve done an initial port of node & field access customizations to the modern version of the site. So we don’t do this work twice, it should wait for events to be migrated to the modern site.

drumm’s picture

Component: Code » Community events
froboy’s picture

@drumm, what's the best way for Event Organizers to follow along with the progress of the migration you mentioned above? We have some initial issues, and it'd be great to connect it to your work.

#3534746: D10 Community Events Design/UX
#3534748: D10 Community Events Migration

Thanks.

heatherwoz’s picture

Issue tags: +Community Events
heatherwoz’s picture

Status: Postponed » Closed (duplicate)
Related issues: +#3276527: Organizers should be able to edit events pages

Closing this as duplicate of #3276527: Organizers should be able to edit events pages. That issue discusses a few more ways of implementing this feature, so I am leaving that one open.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.