Our content person was deleting a post and accidentally deleted the blog entirely in the back office. I don't know quite how she did that, but she did. Anyway, we have the site backed up, both the database and the application.
I thought that we could simply restore the database to the last known good point so we did that.
In the back office I could now see the blog where it was, but the pages would not serve. The data is there and all the entries, but the templates won't serve them any more.
I created a new blog and copy pasted content from the old one to the new and that worked fine, but we only have a few entries so far. This is not a good solution.
In the event of having to restore the database how do I get Articulate to serve those old entries from that database?
Also, if you delete some content, it will go into the recycle bin where you can restore it from you don't need to restore a whole DB (unless of course they also emptied the recycle bin)
You should also delete your umbraco.config file, clear your App_Data/TEMP folder, then restart your site to ensure all caches are rebuilt.
Perfect! Thank you. Exactly what I wanted to hear. I will set up a test this weekend on our QA environment and we can try to create the failure and then fix it.
Much appreciated.
OK we reproduced and this is a fix. I was able to restore from the trash without deleting the App_Data/TEMP folder
Articulate recovery after failure
Our content person was deleting a post and accidentally deleted the blog entirely in the back office. I don't know quite how she did that, but she did. Anyway, we have the site backed up, both the database and the application.
I thought that we could simply restore the database to the last known good point so we did that.
In the back office I could now see the blog where it was, but the pages would not serve. The data is there and all the entries, but the templates won't serve them any more.
I created a new blog and copy pasted content from the old one to the new and that worked fine, but we only have a few entries so far. This is not a good solution.
In the event of having to restore the database how do I get Articulate to serve those old entries from that database?
I suspect you just need to rebuild the caches.
Try deleting
App_Data/TEMP, then recycle your application pool. That should cause the XML content cache to rebuild, as well as the Examine indexes.Also, if you delete some content, it will go into the recycle bin where you can restore it from you don't need to restore a whole DB (unless of course they also emptied the recycle bin)
You should also delete your umbraco.config file, clear your App_Data/TEMP folder, then restart your site to ensure all caches are rebuilt.
Perfect! Thank you. Exactly what I wanted to hear. I will set up a test this weekend on our QA environment and we can try to create the failure and then fix it.
Much appreciated.
OK we reproduced and this is a fix. I was able to restore from the trash without deleting the App_Data/TEMP folder
Thank you guys!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.