Content disappears in the backoffice but is still visible on the frontend
We are currently transferring an existing site into Umbraco but have come across a strange situation.
From time to time, we are finding that content that has been added and successfully published to a page using the back office simply isn't there when we go back to edit it!
Some page contents are fine but others don't show.
There are no error messages and the logs look fine.
Obviously if we publish the page again then the content on the front end then also disappears - which I guess is to be expected.
Looking at the database itself, we can see multiple identical versions of the same property in the cmsPropertyData table where each data column is set to null, with the most recent entry of that property version being the null entry. If we delete these duplicate null entries, the back office content returns.
We've read that this may be an issue with IIS Express/SQL CE, but we're using full IIS and SQL Server 2008 R2.
Does anyone have any idea what might be causing this issue?
Content disappears in the backoffice but is still visible on the frontend
We are currently transferring an existing site into Umbraco but have come across a strange situation.
From time to time, we are finding that content that has been added and successfully published to a page using the back office simply isn't there when we go back to edit it!
Some page contents are fine but others don't show.
There are no error messages and the logs look fine.
Obviously if we publish the page again then the content on the front end then also disappears - which I guess is to be expected.
Looking at the database itself, we can see multiple identical versions of the same property in the cmsPropertyData table where each data column is set to null, with the most recent entry of that property version being the null entry. If we delete these duplicate null entries, the back office content returns.
We've read that this may be an issue with IIS Express/SQL CE, but we're using full IIS and SQL Server 2008 R2.
Does anyone have any idea what might be causing this issue?
Many thanks
Dave
So has nobody ever come across this before?
Just me then :-(
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.