Page-type table deleted in DB, Page-type still listed

There is no "Page type table" in Kentico, at least it is not created by Kentico. All page types are stored in cms_class. To get all existing document types you can try: select * from CMS_class where ClassIsDocumentType = 1. You can also check if you have any node/documents in the tree for the given class:

select nodeid, * from cms_tree where nodeclassid = 123
select * from CMS_Document where DocumentNodeID = 456

You should use API if you want to delete something, not direct SQL statements.

The page-type is a custom "page-type". I edited to add the word "custom".

In my production instance I see the table in the correct location with all the data. In my dev instance there is no table.

I ran that query the the page-type is not in my dev instance. However it is correctly in my production instance.

Then try this select ClassTableName,* from CMS_class where classname = 'custom.page-type'. ClassTableName contains data for your class. Page type is listed i.e. there is a record in CMS_Class. Probably you cannot delete this page type because the table defined in ClassTableName field does not exists.

P.S. Take a look at Page database structure

Brandon,

I assume by the custom table you mean the content table that contains extra fields for your custom page type.

If it's there in one instance, but not in the other, the only thing i can think of is someone or somehow the table was deleted. You may need to recreate the table manually (you can go to your production database, right click on the table and generate the create script table), then once that table exists, try a full sync from your production environment of those pages, hopefully that will re-populate them.

If you are looking to delete that page type completely, and for some reason only the database table deleted and not actual page type, you can look to manually delete it from the CMS_Class table, although manual processes like this wont' be caught by staging.

Trevor I don't have write access to the prod DB, I will try this as soon as I can track down someone from our DB team. Thank you