Contrib.social

Dynamic settings should not be stored via configuration API

Open on Drupal.org →
Created on 30 November 2021, over 3 years ago
Updated 21 August 2023, over 1 year ago

Problem/Motivation

When tagging occurs during cron or manual actions, the timestamp when this happened is stored via configuration API in powertagging.powertagging.CONFIG.yml in the last_batch_tagging variable.

Because this variable changes, the configuration management is always polluted with modifications and difficult to distinguish between legitimate configuration changes. Automated monitoring tools are always reporting changes to config.

Steps to reproduce

Use the module to tag content

Proposed resolution

This variable must be stored using the state API https://www.drupal.org/docs/8/api/state-api/overview →

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇷🇴Romania cristiroma

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

Comments & Activities

Not all content is available!

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

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024