Using the Config Update Manager module, the scheduled content view always appeared to be 'missing'. Even after import, the view was still not linked to the module. Then I noticed that the file name is views.view.scheduler_scheduled_content.yml but the internal view id is id: scheduled_content. It should be id: scheduler_scheduled_content to match.

The report by Configuration Update shows:
wrong view id

Comments

jonathan1055 created an issue. See original summary.

jonathan1055’s picture

jonathan1055’s picture

When the config line is changed to id: scheduler_scheduled_content then the view in config can be matched back to the file that defines it, and we can get a proper comparison.

correct view id

jonathan1055’s picture

jonathan1055’s picture

Status: Active » Needs review

  • jonathan1055 committed 57e2920 on 8.x-1.x
    Issue #2767635 by jonathan1055: Scheduled content view has wrong id
    
jonathan1055’s picture

Category: Bug report » Task
Status: Needs review » Fixed

Wanted to get this fixed, to allow easier testing of #2755665: Restore original access requirement for scheduled content overview..
Also changed the title from 'Content' to 'Scheduled Content', changed the display title from 'page' to 'overview' and added admin descriptions.

  • jonathan1055 committed a1836d8 on 8.x-1.x
    Issue #2767635 by jonathan1055: Scheduled content view has wrong id,...

Status: Fixed » Closed (fixed)

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