Permission missing for Scheduled Content View

Created on 29 January 2024, 11 months ago
Updated 15 March 2024, 9 months ago

Problem/Motivation

I am attempting to access the View called Scheduled Content at the path /admin/content/scheduled. This view is contained in the module at config/install/views.view.scheduler_scheduled_content.yml. This view has an access permission of 'view scheduled content'. This permission is not defined in the 2.x branch version of the module. It IS defined in the previous 8.x branch version of the module.

Attempting to view this View results in an Access Denied response, even as the UID 1 user.

Steps to reproduce

Install the module and attempt to access /admin/content/scheduled. You should get an Access Denied response. Check for permissions at /admin/people/permissions/module/scheduler. You find no such permission 'view scheduled content' defined which the View requires.

Proposed resolution

Attached patch adds back the permission as was defined in the 8.x branch.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Closed: works as designed

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jaydub

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @jaydub
  • Open in Jenkins β†’ Open on Drupal.org β†’
    Core: 10.2.x + Environment: PHP 8.1 & MySQL 8
    last update 11 months ago
    227 pass
  • πŸ‡ΊπŸ‡ΈUnited States jaydub
  • Status changed to Closed: works as designed 11 months ago
  • πŸ‡ΊπŸ‡ΈUnited States jaydub

    Ok I looked into this more closely and it looks like the old permission is not dynamically set and our issue was the the Views defined in the old version of the module did not have their access settings automatically updated upon upgrading to the 2.x version. Going to close this for now.

  • πŸ‡§πŸ‡ͺBelgium fernly

    Thank you for elaborating.
    I had the same issue and even setting the permission right in the View, still didn't work.

    Solution: there appeared to be 2 Views "Scheduled content" and "Scheduled content revisions" having the same path /admin/content/scheduled. The latter was still configured with the wrong access rule.

Production build 0.71.5 2024