Closed (fixed)
Project:
Token Content Access
Version:
3.0.2
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2024 at 22:05 UTC
Updated:
19 Mar 2026 at 15:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
drupgirl commentedComment #3
london6339 commentedEven when I import config that adds
forced: trueorforced: 1to the TCA content type yml, the yml reverts back to the previous one.Comment #4
wgoley06 commentedHi, 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: false
I tried changing themes and uninstalled additional modules that might conflict but having no luck.
Anyone else figure out the issue on this one?
Comment #7
tavib47 commentedI create a MR to fix this issue. I found out that "force" key is missing from
TcaSettingsconfig entity.I'm also attaching the patch.
Comment #8
tavib47 commentedhttps://git.drupalcode.org/project/tca/-/merge_requests/8
Comment #9
mauro_ commentedHi, this issue should be fixed in the latest release. Thanks for the contributions @london6339 @drupgirl @wgoley06 @tavib47
Comment #11
mauro_ commented