Content types already have a disabled property:
{
"_config_name": "node.type.page",
"type": "page",
"name": "Page",
"description": "Add a page with static content, like the 'About' page.",
"settings": {
...
},
"base": "node_content",
"module": "node",
"node_preview": "1",
"help": "",
"modified": true,
"disabled": false, <----- HERE!
"has_title": true,
"title_label": "Title",
"orig_type": "page"
}
But we are not exposing any way to enable/disable content types in the UI. Lets do that
Related article: Drupal 7: How to disable a content type
The database table where content types are stored is
node_type. And there's a columndisabledin it. We can disable a content type by changing the column value to1.
GitHub Issue #:
3883
Recent comments
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5
Worked like a charm! Exactly what I envisioned... now I can edit the ruby text right in the editor, sweet:) Thank you! For those who may have a similar issue, try TinyMCE, create a new "text...
Specific tags to work in CKEditor 5
Yes, you can use TinyMCE on some content and CKEditor5 in others. There is no problem having both enabled on a system.
Specific tags to work in CKEditor 5