Restrict visibility per content type

Open on Drupal.org →

Created on 27 June 2022, about 2 years ago

Updated 2 April 2024, 3 months ago

Problem/Motivation

Sitewide alerts can be restricted by a list of routes. However when displaying them on admin pages, the routes are not always consistent and could be more accurately targeted through content types, similar to block visibility. For our use case, we mainly use these alerts on admin pages as it is a decoupled cms so the ability to target by content type would be helpful.

e.g. if I have an "Event" content type, i can easily set an alert to be visible on /node/add/event. However, any existing events (or after node save), that route is no longer /node/add/event but now node/[nid]/edit

Steps to reproduce

- Allow sitewide alerts to be visible on admin pages through config
- Create a sitewide alert and restrict it to the /node/add/event (or other content type)
- Visit /node/add/event and see the alert.
- Save the node, the alert will disappear (not a bug, as it is a different route now)

Proposed resolution

Add an option for restricting alerts by content types under an alert's visibility options. Can be conditionally visible similar to the current routes field. Thinking maybe a separate checkbox "Limit by Content Type" that then surfaces a checkbox list of available content types.

This would enable an alert to be set for the Event content type instead of a specific route, handling node/add/* and node/*/edit.

✨ Feature request

Status

Active

Version

2.0

Component

Code

Created by

🇺🇸United States tjh

Live updates comments and jobs are added and updated live.

Incomplete comments

Sign in to follow issues

Merge Requests

!50Restrict visibility per content type
Open
🇦🇺Australia sanjay.maharjan
updated 3 months ago

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 5 months ago →
🇦🇺Australia sanjay.maharjan
Hi,
Having content type restriction would be really helpful with this module.

I have tried to add the restriction per content type and created this patch.

Note: please run update.php after applying this patch ( or drush updb ).

Thank you
Open in Jenkins → Open on Drupal.org →
Core: 10.2.x + Environment: PHP 8.1 & MySQL 8
last update 5 months ago
13 pass, 2 fail
Comment 3 months ago →
🇦🇺Australia sanjay.maharjan
Updated the patch file with minor code changes. This works without any error in my project.
Open in Jenkins → Open on Drupal.org →
Core: 10.2.x + Environment: PHP 8.1 & MySQL 8
last update 3 months ago
13 pass, 2 fail
Merge request !50ISSUE-3292957: Restrict visibility per content type. → (Open) created by sanjay.maharjan
Open on Drupal.org →
Core: 9.5.x + Environment: PHP 7.4 & MySQL 5.7
last update 3 months ago
Waiting for branch to pass
Pipeline finished with Failed
3 months ago
Total: 265s
#135001

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024