Drupal: the content type in the database is not in the list of content types in Structure> Content Types

Some time ago, I created two types of content: “protocol” and “protocol2”. They were a little different, and I was not yet sure which one was best for my purposes, so I tried both and created some content for each of them. After a little testing, I came to the conclusion that “protocol2” was the one that I was going to use, and that I wanted it to be called “protocol” and not “protocol2”. But I wanted to keep a different version of the protocol content type, so I taught that I would just write my names.

So I tried to flip their names, but during this process something went wrong with the “protocol2” content type that I wanted to use, and it just disappeared. Or I taught. In any case, I renamed 'protocol' to 'protocol1' (name and machine name). And recreated the one that disappeared. I gave him the name "Protocol" and tried to give him the name "protocol" of the machine name, but that did not work, so I had to call him protocol2 again.

Now I found that in the node_type database, the database actually has a content type called “protocol” of the machine name, which does not appear when I look at “Structure”> “Content Types” on the page. Can I just delete it from this table or is there any other way to do this?

I used Organic groups and had a content type like "protocol" or "protocol2" associated with some groups (I don’t remember which one). And I think this overshadows one of the views on the band page. A list with the heading "Publish content for the group" consists of "Mail" and an empty list item. Where can I manage this list? Shouldn't this be a point of view?

+4
source share
1 answer

In the node_type table node_type make sure locked is 0 and disabled is 0 for all of your protocol types. Change all their orig_type values ​​to match their current type values. Clear the Drupal cache in admin/config/development/performance .

Now they should all appear on your Content Types list, and you can work from there.

This is an active bug for Drupal 8, with the ability to backup any patch, under Drupal issue 515454 .

+3
source

All Articles