Deleted Template is still registering as a Post Types Template

This support ticket is created 4 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-	-	9:00 – 13:00
14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-	-	14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

Tagged: Content Templates, Views plugin

This topic contains 1 reply, has 2 voices.

Last updated by Jamal 4 years, 10 months ago.

Assisted by: Jamal.

Author

Posts

September 22, 2020 at 5:36 pm #1786381

costasT

I created a template last night but was unhappy with the way things came out. I made sure to delete all fields, taxonomies, post type & template. I cleaned my database, did a restore from a previous backup & cleaned the database again. I added a new Post Type & created fields. When I went back to dashboard, I noticed that the template displaying for the post type was deleted.

When I click the template name link, I get this message:
You attempted to edit a Content Template that doesn’t exist. Perhaps it was deleted?

I tried looking around in the support forums and docs, but cant seem to find anything that has helped me rectify this issue. Any help would be much appreciated. Thank you.

September 23, 2020 at 8:50 am #1787285

Jamal

Hello and thank you for contacting the Toolset support.

Based on the error message you are receiving, I would say that the template is still in the trash of the content templates. Go to Toolset->Content Template, and check above the table if you have the link to the trash.
If the content template is completely deleted from the website, I wonder where do you get this link to edit it? I might need to take a closer look at your backend to check this. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **