Historically event organizers have used a shared Google Sheet to try and ensure that their chosen event dates don't overlap with each other: https://docs.google.com/spreadsheets/d/1AwFTuPQhXiblAqtqe7ckpZIUHwyy9Q2X...

Now that we have /community/events we can likely replace this with a d.o view

Requirements

  • Create view as a block to be placed on a page
  • Columns this should include:
    • Event name
  • Event status (proposed, confirmed, cancelled, etc)
  • Event type
  • Event dates
    • Multi-value field, so add twice
    • - Start date
    • - End date
  • Sorted by start date - no exposed sorting
  • Filtered by events that end after the current date
  • Issue fork drupalorg-3317296

    Command icon Show commands

    Start within a Git clone of the project using the version control instructions.

    Or, if you do not have SSH keys set up on git.drupalcode.org:

    Support from Acquia helps fund testing for Drupal Acquia logo

    Comments

    crawleyhost created an issue. See original summary.

    hestenet’s picture

    Issue summary: View changes
    hestenet’s picture

    Issue summary: View changes
    hestenet’s picture

    Work in progress on this feature is here:
    https://caleb-drupal.dev.devdrupal.org/community/events/dates
    (htaccess - user: drupal / pass: drupal)

    hestenet’s picture

    One of the feature requests from event organizers in Slack was to attach a CSV export to this as well.

    hestenet’s picture

    Also needs status column: 'proposed, confirmed, canceled' etc

    froboy’s picture

    @crawleyhost this is very exciting! We're discussing at our EOWG meeting and a few initial thoughts/requests:

    Additional columns:
    - Event Type
    - Country/Continent (not sure about this, but some filterable location would be nice)

    Exposed filters:
    - Filter by title
    - Filter by type

    Sorting:
    - Sortable columns should be sortable (at minimum, Start Date)
    - Default sort: Start Date, descending from newest to oldest

    Also, having the standard view summary ("Showing __ of ___ events") would be nice for us when trying to get data out of it.

    Finally, @seantwalsh suggests the filters could be more like facets on the side, similar to https://www.drupal.org/community/events/past-events?field_event_type_val..., although keeping them on the top might give more width to let the table expand.

    Thanks for your work on this! Looking forward to seeing it develop.

    kclarkson’s picture

    This is sooooo Amazing!! Great work.

    1. The width of the page - Would be nice to have the table full page width so we can view columns
    2. CSV Export View - Add a view that allows us to export all of the events. This way we can geek out with our own spreadsheets.
    3. Filter by Continent and Country would be good
    4. Timezone Display - Can we get this set to our browsers time zone?

    B_man made their first commit to this issue’s fork.

    drumm made their first commit to this issue’s fork.

    • drumm committed ae8ef0b on 7.x-3.x authored by crawleyhost
      Issue #3317296 by crawleyhost, drumm, hestenet: Community events:...
    B_man’s picture

    This has been deployed and can be found here: https://www.drupal.org/community/events/date-check

    johnpicozzi’s picture

    This is looking really good. Found a bug when filtering by DrupalCamps, US, and Proposed. The reset button repeats and only the last one works.

    multiple reset buttons on filter form

    Using Firefox on a Mac.

    B_man’s picture

    Thanks for the report, would you be able to give me your browser version? I'm unable to reproduce that issue on my end.

    drumm’s picture

    Status: Active » Fixed

    Marking fixed since everything is deployed.

    If this is reproducible, also try without Dreditor, or any other extensions, and open a new issue with the specific details.

    johnpicozzi’s picture

    An update - Disabling Drerditor resolves the issue noted above with multiple reset buttons.

    drumm’s picture

    We have change Drupal.org’s behavior to work well with Dreditor in the past, however this is all from stock Drupal modules. The Reset button is likely added via the Drupal JS behaviors API, which Dreditor invokes multiple times, without something preventing it from being attached twice. This is likely done in Views, so it should be fixed upstream.

    I believe we haven’t seen this before since most Views on Drupal.org are configured to not have the exposed filters reset button. Removing it should also be a doable option.

    • drumm committed ae8ef0b1 on block-on-login authored by crawleyhost
      Issue #3317296 by crawleyhost, drumm, hestenet: Community events:...

    Status: Fixed » Closed (fixed)

    Automatically closed - issue fixed for 2 weeks with no activity.