Contrib.social

Add Configuration Guard Rails

Open on Drupal.org →
Created on 3 May 2023, about 1 year ago
Updated 4 May 2023, about 1 year ago

Problem/Motivation

The group subscription module makes a few assumptions around how the module will be configured that are documented in the README but not enforced in code. We need to add some guard rails and guidance to prevent admins from accidentally configuring the module in a way that will break the functionality and ensure everything the module needs is properly enabled.

  1. The module configuration page should explicitly state which theme will be used for emails. This is the active front end theme but this should be stated clearly so admins don't have to dig into the README to know
  2. Site-wide announcements: the list of available nodes to be used for site-wide announcement subscriptions should never include any node types that are already configured as group content.
  3. Site-wide announcements: once the administrator has selected the content type they want to use for site-wide announcements we should display help text below letting them know they should enable and configure the site-wide announcement display for the type they selected (and supply a link to that configuration page) If configured the text should update on future views to show it is enabled.
  4. Group content: when enabling the gnode functionality for a given group type we should not list a node type if that type is already configured to be used for site-wide announcements.
  5. Group content: when enabling group subscriptions for a given node type the cardinality for that node type must currently be set to 1. We need to add validation to this form at a minimum to ensure the cardinality is set to 1 if group subscriptions are enabled. We may want to go so far as to automatically update the value in this field as disable it.
  6. Group content: when enabling group subscriptions for a given node type we should display help text below letting the user know they should enable and configure the immediate and daily displays for the type they are editing (and supply a link to that configuration page) If configured the text should update on future views to show it is enabled.
  7. If possible, do not show the group subscription based display options for a given content type unless the content type has been enabled for that use
  8. The module .info.yml file should also include a dependency on the drupal:block module as this module does create a block to be placed on group pages as a shortcut for managing individual group subscriptions
📌 Task
Status

Active

Version

3.0

Component

Code

Created by

🇨🇦Canada JayDarnell Guelph, Ontario

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

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024