I'm in version 7.5.14 and having an issue that no matter what I do content is still available. This content is accessible through UmbracoHelper.TypedContent
So I've completely deleted this content AND cleared the recycle bin. I can't even find it in the database. I've republished the entire website, disabled XML caching, deleted & rebuilt the example index, and restarted the website. None of this makes a difference.
How is this possible? Does Umbraco cache the content somewhere I'm not looking?
It sounds somewhat similar. I've searched most of the database and can't seem to find it anywhere. I can even spit out the node name through UmbracoHelper. Which makes no sense. Where is it storing this?
I've search these tables:
cmsContent, cmsContentXml, cmsDocument, cmsPreviewXml, umbracoNode
None of these IDs are anywhere. Pulling my hair out here.
Deleted content will not disappear
I'm in version 7.5.14 and having an issue that no matter what I do content is still available. This content is accessible through UmbracoHelper.TypedContent
So I've completely deleted this content AND cleared the recycle bin. I can't even find it in the database. I've republished the entire website, disabled XML caching, deleted & rebuilt the example index, and restarted the website. None of this makes a difference.
How is this possible? Does Umbraco cache the content somewhere I'm not looking?
I've also manually looked into the Internal index and don't see those nodes in there.
Can this be similar the problem I had this summer? I didn't find any solution, and created a whole new site .. https://our.umbraco.org/forum/templates-partial-views-and-macros/86825-how-to-delete-ghost-links-that-appear-only-in-frontend
It sounds somewhat similar. I've searched most of the database and can't seem to find it anywhere. I can even spit out the node name through UmbracoHelper. Which makes no sense. Where is it storing this?
I've search these tables: cmsContent, cmsContentXml, cmsDocument, cmsPreviewXml, umbracoNode
None of these IDs are anywhere. Pulling my hair out here.
Also unfortunately making a new website isn't an option since there is about 3 months of work in this site.
It appears to have come from /App_Data/preview. Deleting that config seems to have solved my problem.
is working on a reply...