Contrib.social

'auto' is not a supported key

Open on Drupal.org →
Created on 9 January 2025, 3 months ago

Problem/Motivation

Hello, I am having an issue when trying to update any configuration. Anytime I change anything, I get an error that says:

"'auto' is not a supported key."

If I disable all directives that have an *auto next to the time (and thus has an Auto Sources box) this error goes away. For example,. the script-src directive.

It seems that this textarea field is causing issues.

Steps to reproduce

Enable CSP module

Open Configuration

Verify that some of the *auto labelled directives are there, and there are Auto Sources.

Try to make any change and save.

For reference, I also have the Security Kit module enabled. I'm not sure if this would be causing some issues also.

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

michael.garrido

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

Comments & Activities

  • Issue created by @michael.garrido
  • Comment 3 months ago →
    🇺🇸United States anawillem

    I am having the same issue. And also have the Security Review module installed.

  • Comment 3 months ago →
    mvnovick

    I am also having the same issue, but I do not have the Security Review module installed.

  • Comment 3 months ago →
    🇺🇸United States jrearick Iowa

    I'm getting the same.

    I wonder if it's a regression in the 2.2.x release → . There was a lot of config validation work done.

    I downgraded to 2.2.0-rc1, but that seems to be a duplicate tag of 2.2.0.

    Downgrading to 2.1.1 seems to have worked.

  • Comment 3 months ago →
    System Message
    • gapple → committed a64ff168 on 2.x 
      Issue #3498591: Auto sources in config form preventing config changes
  • Comment 3 months ago →
    🇨🇦Canada gapple

    Thank you for the bug report.

    The disabled field value was still in the form data and getting set to config when it shouldn't have been. 2.2.1 is now available with a fix 🙂.

    ----

    SecKit and CSP are fine to work together, as long as the CSP setting in SecKit are not used since one module would overwrite the other's header value. (CSP will add a warning to the site status if it detects Seckit's CSP fields are enabled).

  • Comment 2 months ago →
    System Message

    Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024