Skip to content

Add Token Filter module to GovCMS #1598

@gargsuchi

Description

@gargsuchi

Please provide the Drupal.org URL for the module
https://www.drupal.org/project/token_filter

What value does this module/package add to GovCMS?
Provides a simple WYSIWYG integration, allowing content editors to use Drupal Tokens directly in their WYSIWYG content. Reduces the need for developer resources when setting up or maintaining GovCMS SaaS projects that use RaC services.

Is the module Drupal 11 compatible?
Yes

Please provide a brief outline of what this module does.
Provides a simple WYSIWYG integration, allowing content editors to use Drupal Tokens directly in their WYSIWYG content. Helps with customised content and explainability aspect of Rules as code.

** Who does this module benefit: **
[ ] end users
[X] content editors
[X] site builders
[ ] themers
[ ] developers

** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?**
Addition of custom _preprocess functions to GovCMS website themes bespoke to each OpenFisca project

** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.**
Yes. This module alters the HTML by changing the tokens into their values within the WYSIWYG. The other alternative would be to add custom hook_preprocess functions in the theme layer - which will be bespoke to each project.

** What is the maintenance and support status of the module. Describe the issue queue activity.**
The module is considered feature-complete by its maintainers and is in “maintenance only” mode. There are 180 issues in the queue, but only 8 of those are open.

** What permissions are needed to utilise the module (and are any new permissions provided by the module)?**
The module does not define new permissions. It is a filter that can be enabled on a Text Format, and the permissions of the Text Format apply on the functionality of this module.

** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?**
No, it does not modify database structure.

** Is the module designed to capture anonymous user data?**
No. It does not capture any user data.

** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.**
The output of the module is cacheable.

** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?**
The module is maintained by several maintainers who are prolific contributors. 2 of them are Australia based. The module is used by more than 60,000 sites (as per the drupal.org page).

** Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestmoduleunder investigationRequest has been added to the backlog to be investigated.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions