Problem/Motivation

Allow building event views that include unpublished events, but only show them for users who have permission to see them.

Proposed resolution

Implement "Published status or admin user" Views filters for event series and instances, similar to those provided by core for nodes, media, etc.

User interface changes

Adds a "Published status or admin user" Views filter option for eventseries and eventinstance views.

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:

Comments

muriqui created an issue. See original summary.

muriqui’s picture

Status: Active » Needs review

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

dmundra’s picture

Assigned: Unassigned » dmundra

Will review this one as well

dmundra’s picture

Assigned: dmundra » Unassigned
Status: Needs review » Reviewed & tested by the community

Tested with the following steps. Thank you @muriqui

  1. Create an event series, but leave it unpublished.
  2. Create a simple Views page of event series entities, and configure it to use the "Published status or admin user" filter.
    1. () Visit the view as an admin and confirm that it shows the unpublished event series.
    2. () View the view as anonymous and confirm that it does not show the event series.
  3. Create a simple Views page of event instance entities, and configure it to use the "Published status or admin user" filter.
    1. () Visit the view as an admin and confirm that it shows the unpublished event instances.
    2. () View the view as anonymous and confirm that it does not show the event instances.

  • muriqui committed d9324d81 on 3.0.x
    feat: #3557676 Add "Published status or admin user" Views filters
    
    By:...
muriqui’s picture

Status: Reviewed & tested by the community » Fixed

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.

Status: Fixed » Closed (fixed)

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