config ignore property for simplenews not ignored

Created on 3 September 2021, about 3 years ago

Updated 4 January 2024, 11 months ago

Problem/Motivation

We have a default simplenews letter, but we allow users (in our multisites) to override some of the values. I added this to our config ignore:

  - simplenews.newsletter.default.name
  - simplenews.newsletter.default.description
  - simplenews.newsletter.default.from_name
  - simplenews.newsletter.default.from_address

But it still resets on config import. In the UI, if the user changed the values, it shows under changed as simplenews.newsletter.default and not under the section for ignored configuration entities. I thought we were able to specify down to the config property in config ignore.

The simplenews config file (simplenews.newsletter.default.yml) looks like:

uuid: 1d4bb4f1-16db-4223-b6ae-1ac57889ccbd
langcode: en
status: true
dependencies: {  }
_core:
  default_config_hash: hj6zGNwndnW_J6lKfFcg-tY5e5YqWfgXyt0qioGtXL8
name: 'Our newsletter'
id: default
description: 'Newsletters for notable news at our awesome place of work.'
format: html
priority: 0
receipt: true
from_name: 'Our Leaders'
subject: '[simplenews-newsletter:name] [node:title]'
from_address: ouremail@example.com
hyperlinks: false
allowed_handlers:
  0: '0'
  simplenews_all: '0'
new_account: none
opt_inout: double
weight: 0

🐛 Bug report

Status

Closed: outdated

Version

2.3

Component

Code

Created by

🇺🇸United States shelane

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment 11 months ago →
🇨🇭Switzerland bircher 🇨🇿
This issue is being closed because Config Ignore 2.x is deprecated.

The new 3,x version has been re-written from the ground up and works in a totally different way, yet it provides the same backwards compatible functionality. All the 2.x tests pass in 3.x and the 3.x codebase is easier to maintain.
Users of 2.x are strongly encouraged to upgrade to 3.x, as there is a very simple update path.

So likely this issue is no longer relevant. If you think that this issue still applies please open it again and target the new branch. All issues on the 2.x branch were closed in bulk.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024