I had a Landing page like www.website/landingpage/abc.
I've unpublished it because I wanted to create a new ne with a different nodeType.
First I've unpublished it but I've seen that the page was still available.
I've delete the page ... still available
I've Emptied the recycle bin ... still there.
I've deleted the app_data/umbaco.config ... republished the website ... still there.
I've searched for the nodeID in the DB ... I didn't found it anywhere except the log table with 'deleted' as the last status.
Even stranger than this the page is available on the www.website/abc and I never created any aliases for it.
I've ran an XSLT script to display <xsl:value-of select="$currentPage/@id"/> ... surprise!! it's showing the parent nodeID. And it has a different value for www.website/landingpage/abc and www.website/abc.
Note: the page doesn't physically exists on the website. Publishing / Unpublishing other pages is working fine.
Delete Page still available
Hello,
This is a strange one ...
I had a Landing page like www.website/landingpage/abc.
I've unpublished it because I wanted to create a new ne with a different nodeType.
First I've unpublished it but I've seen that the page was still available.
I've delete the page ... still available
I've Emptied the recycle bin ... still there.
I've deleted the app_data/umbaco.config ... republished the website ... still there.
I've searched for the nodeID in the DB ... I didn't found it anywhere except the log table with 'deleted' as the last status.
Even stranger than this the page is available on the www.website/abc and I never created any aliases for it.
I've ran an XSLT script to display <xsl:value-of select="$currentPage/@id"/> ... surprise!! it's showing the parent nodeID. And it has a different value for www.website/landingpage/abc and www.website/abc.
Note: the page doesn't physically exists on the website. Publishing / Unpublishing other pages is working fine.
I hope someone can tell me what is going on.
Cornel
Hi Cornel - welcome to our :)
This sounds like an odd issue indeed.
Can you tell us a bit about the version of Umbraco you're using and the server specs?
Sounds like a weird "ghost node" issue - but let's see if we can figure it out based on further information.
/Jan
is working on a reply...