- Issue created by @london6339
Even when I import config that adds forced: true or forced: 1 to the TCA content type yml, the yml reverts back to the previous one.
- πΊπΈUnited States wgoley06
Hi, unless I've overlooked another patch, I still seem to be running into this issue with the enforce token to save on specific nodes. I've tried to export configurations, update the config file, and reimport but its not saving still. I see in the DB that the
SELECT name, data FROM config WHERE name = 'tca.settings';
+--------------+----------------------------------------------+
| name | data |
+--------------+----------------------------------------------+
| tca.settings | a:1:{s:19:"enforce_token_usage";s:4:"true";} |
+--------------+----------------------------------------------+enforce_token_usage: true
uuid: faf053eb-da89-4669-a1db-c7b864b9e690
langcode: en
status: true
dependencies:
config:
- node.type.estimate
id: node_type_estimate
active: 1
token: required
public: falseI tried changing themes and uninstalled additional modules that might conflict but having no luck.
Anyone else figure out the issue on this one?