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
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list