Quantcast
Channel: SharePoint 2013 - General Discussions and Questions forum
Viewing all articles
Browse latest Browse all 26374

Changes to Wiki pages are lost if open for > 30 minutes

$
0
0

If a user is editing a Wiki Page and they have it open for more than 30 minutes, then when they press Save their changes are lost and the page refreshes with the previous saved version and there is no record in the Version history of the change.

This is repeatable and prior to 30 minutes the problem doesn't occur. Because it only happens after 30 minutes, we weren't seeing it all the time and our users thought they were doing something silly, but the continued loss of large changes to documents has caused us to investigate further. Unfortunately because it happens after 30 minutes, there is likely to be a lot of changes that are lost. This unreliability is a major problem for us: imagine if a user edited a Word document and when they saved they lost everything.

The problem doesn't seem to occur for Webpart pages.

We run standalone sharepoint (not office 365) and we use IE 10, we have also tested with Firefox and Chrome and exactly the same thing happens.

We have applied the June 2013 CU KB281746 (and the March prereq KB2768000) because we were hoping that it was a history issue and that this would fix it:

• When you make some changes to a Wiki page on a SharePoint Server 2013 site, the changes are not tracked in page history view.

I have worked extensively with SP2007 and have never seen this before.

There is another reference to this in this forum, and I wonder if the problem wasn't related to the amount of time the page was open and the poster didn't realise:

http://social.technet.microsoft.com/Forums/sharepoint/en-US/2889f5a8-5fc1-4936-9304-d5e2a5a9a154/bug-in-sharepoint-2013-rtm-wikis

There are also numerous reports of this on the 365 site with no response:

http://community.office365.com/en-us/forums/154/t/151944.aspx?PageIndex=2

Does anybody have any thoughts on whether this is something in our environment or a bug. And if it's a bug, Microsoft, can we know when it will be fixed?


Viewing all articles
Browse latest Browse all 26374

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>