Create new "power user" flag to disable warnings and validation

Created on 20 June 2025, 4 days ago

Via #3530906-6: Improve interaction with HTML filter β†’ , create a `power_user_mode` boolean config variable that is not modifiable via the UI (only by directly modifying config) that does disables all warning related to configuration of the Markdown Easy text filter, including its relationship with "Limit allowed HTML tags."

This would affect validation and messages in:

  • _markdown_easy_filter_format_form_submit()
  • _markdown_easy_filter_format_edit_form_validate()
  • markdown_easy_requirements()

Test coverage to confirm validation and messages are disabled are necessary.

An addition to the "Advanced" documentation page β†’ will also be necessary to demonstrate how to enable this new setting.

Other potential variable names are:

  • skip_filter_enforcement
  • disable-all-warnings

Personally, I think the variable name should be less-specific in case we want to add (subtract?) additional functionality to it in the future.

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States ultimike Florida, USA

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

Comments & Activities

  • Issue created by @ultimike
  • πŸ‡§πŸ‡ͺBelgium Dries

    Thanks for opening this. My personal preference would be to introduce multiple config variables rather than a single catch-all flag like power_user_mode. For example, something like:

    • skip_filter_enforcement
    • skip_html_input_stripping

    Personally, I would want to disable both, but I could see others wanting to disable just one or the other.

    As more options get added over time, I could see power users wanting different combinations of behavior. Having discrete flags keeps it flexible and future-proof.

    You could always do both. Support individual variables, but wrap them like this:

    if ($config['power_user_mode'] ?? FALSE) {
      $skip_filter_enforcement = TRUE;
      $skip_html_input_stripping = TRUE;
    }
    

    This could give us the best of both worlds: fine-grained control and a simple, global override.

Production build 0.71.5 2024