You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Create a new property with key `contentblocks.disabled` - please make sure to check your spelling. Set the value to 1 if you want to disallow ContentBlocks on this template, set the value to 0 (or an empty string) to allow it.
Copy file name to clipboardExpand all lines: en/02_ContentBlocks/v1.x/04_Configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ When this setting is turned on, ContentBlocks will no longer be used. This setti
51
51
1. First decide if you want to _whitelist_ templates (in which case you disable ContentBlocks globally, and then enable it per-template), or _blacklist_ them (in which you enable ContentBlocks globally, but disable specific templates). Set the `contentblocks.disabled` system (or context) setting accordingly.
52
52
2. Edit the template you want to enable/disable. Navigate to the Properties tab.
53
53
3. Unlock the default properties by clicking the "Default Properties Locked" button in the grid. (While for snippets and plugins you would typically create a custom property set, that's not currently possible for templates.)
54
-
4. Create a new property with key `contentblocks.disabled` - please make sure to check your spelling. Set the value to 1 if you want to allow ContentBlocks on this template, set the value to 0 (or an empty string) to disallow it.
54
+
4. Create a new property with key `contentblocks.disabled` - please make sure to check your spelling. Set the value to 1 if you want to disallow ContentBlocks on this template, set the value to 0 (or an empty string) to allow it.
55
55
5. Repeat for other templates you are whitelisting/blacklisting.
56
56
57
57

0 commit comments