- Issue created by @poker10
- πΈπ°Slovakia poker10
Just to note, I have not found an option to turn off the Navigation module feature, that you cannot click on the menu item unless it is a last child.
- π¦πΊAustralia pameeela
This is diabolical. The Scheduler module adds these views for each supported entity type even if it's not enabled for any bundles of that entity type. I think a good workaround is to disable these views by default. It's extremely unlikely to me that anyone ever schedules the publishing of taxonomy terms or media and if someone is doing that they can figure out how to enable the views!
But this is also an ongoing issue in Navigation π Second level menu items can't be reached if they have children Active that we can't fully solve here but we can eliminate this instance of it.
- π¦πΊAustralia pameeela
Updated content type base to disable these views by default.
-
phenaproxima β
committed 87c93eca on 1.x authored by
pameeela β
Issue #3495134 by pameeela, poker10: Disable Scheduler's views for...
-
phenaproxima β
committed 87c93eca on 1.x authored by
pameeela β
-
phenaproxima β
committed 356998f2 on 1.0.x authored by
pameeela β
Issue #3495134 by pameeela, poker10: Disable Scheduler's views for...
-
phenaproxima β
committed 356998f2 on 1.0.x authored by
pameeela β
-
phenaproxima β
committed 69f9dc70 on 1.0.x
Revert "Issue #3495134 by pameeela, poker10: Disable Scheduler's views...
-
phenaproxima β
committed 69f9dc70 on 1.0.x
- π¦πΊAustralia pameeela
It's not this one, it's related to π Update default content to add moderation state Active
Adding non-existent permissions to a role is not allowed. The incorrect per missions are "use basic_editorial transition archive", "use basic_editorial transition archived_published".
But those permissions were removed. Something's not quite right.
-
phenaproxima β
committed 44c03233 on 1.0.x
Revert "Revert "Issue #3495134 by pameeela, poker10: Disable Scheduler's...
-
phenaproxima β
committed 44c03233 on 1.0.x
- πΊπΈUnited States phenaproxima Massachusetts
Turns out HEAD in this branch is failing even with the reverted commit. So, reverting the revert. (See https://git.drupalcode.org/project/drupal_cms/-/jobs/3768287#L78)