uBlogsyPost is accessible in frontend but not in backend
Hi. I've encountered an instance of a blog post that is accessible (via direct link) in the frontend but not listed in the Umbraco backend. Tried to query the said umbracoNode was already deleted previously.
What I'd like to know is:
Why is the blog post still accessible after deletion? And how should this be fixed (when the item cannot be seen from Umbraco)?
Would it still be possible to "un-delete" this blog post and make it accessible in Umbraco?
1. It could sounds like the site has cached the blog post, have you tried to clear the browser cache.
2. If you have deleted the blog post from the Umbraco backend, have you tried to look at the recycle bin in the Content section, to see if you can find the deleted blog post there (if so), you could try to restore it again.
This are just my thoughts on what you could try. Hope it helps,
Just to be clear, this (the blog post being accessible in frontend but not in backend) is not a uBlogsy bug but rather an intermittent bug in Umbraco. Is this understanding correct?
Any particular reason/cause as to why this happens?
uBlogsyPost is accessible in frontend but not in backend
Hi. I've encountered an instance of a blog post that is accessible (via direct link) in the frontend but not listed in the Umbraco backend. Tried to query the said umbracoNode was already deleted previously.
What I'd like to know is:
Thanks.
Hi Alex,
Here are my thoughts on this and it may help you.
1. It could sounds like the site has cached the blog post, have you tried to clear the browser cache.
2. If you have deleted the blog post from the Umbraco backend, have you tried to look at the recycle bin in the Content section, to see if you can find the deleted blog post there (if so), you could try to restore it again.
This are just my thoughts on what you could try. Hope it helps,
/Dennis
Re: 1, tried to clear the cache by opening and saving the web.config (application restart), but the blog post is still accessible.
Re: 2, managed to find the uBlogsyPost in the Content recycle bin. When I selected the said item, the following error was shown:
This is an umbraco bug that pops up every now and then... the easiest thing to do is to clean it up directly with sql.
You can manually change trashed, parentId, and the path in sql and it should put the node back.
Just to be clear, this (the blog post being accessible in frontend but not in backend) is not a uBlogsy bug but rather an intermittent bug in Umbraco. Is this understanding correct?
Any particular reason/cause as to why this happens?
It's possible that your umbraco cache file contains a node which has been deleted. Thus, the public site will still show the page.
This is can occure in umbraco 4.x. Don't ask my how to protect against it though :)
is working on a reply...