Bug: View after Save loses text

This was previously reported indirectly as the reason for SavePreviewTextOnServer, see discussion there and in ViewAfterSaveCachesOldPage.

Test case

Intermittent...

• Edit a page, make a change, Preview and Save
• (sometimes) your change will not show up on the View page
• Hit Ctrl/Refresh (IE) or Shift/Reload (Netscape/Mozilla) to bypass any proxy caches
  • If the change shows up, you probably have the cache-related variant of this bug, please see ViewAfterSaveCachesOldPage
  • If not, try using another browser to get the view page, e.g. OperaBrowser or MozillaBrowser - if you don't have another browser, try using another PC.
• If you still get the old page, you have the non-cache-related variant of this bug
  • I tried Lynx and Mozilla and still got the old page, so it is not cache-related (in this variant) - no proxy caches in use by any browser

Environment

CGI.pm version: 2.46

Proxy cache: none

-- RichardDonkin - 19 Mar 2002

Follow up

The two variants of this bug are somewhat confusing - this one is definitely not a caching bug, as I don't use a proxy cache at all and trying Ctrl/Refresh and other browsers did not reveal the real page was being improperly cached.

I've instrumented our local TWiki to record the $text value for all pages saved - this will help work out if it's a TWiki bug or (more likely) in CGI.pm, InternetExplorer or Apache.

NOTE: If you get this bug, please record your CGI.pm version, and any use of proxy caches. This bug has been lingering around for many months...

-- RichardDonkin - 19 Mar 2002

Follow up

Same error: My Environment

CGI.pm version: 2.68

Proxy cache: none

-- PetricFrank - 16 Apr 2002

I assume you tried Ctrl/Refresh or Shift/Reload, and this didn't help? If so, this does seem to be this bug. It would be worth recording the $text value on all save operations (using writeDebug), to help narrow down whether this bug is in TWiki or somewhere else.

-- RichardDonkin - 17 Apr 2002

Fix record

I really don't believe this is a TWiki bug, but is (if it still exists) a bug in browser/web server interaction, or incorrect configuration, or finger trouble. Everyone is aware of it and this report adds no value, so I'm closing it as unreproducible and adding a feature request to add the "solution" to a FAQ - see AddSaveProblemAnalysisToFaQ.

-- CrawfordCurrie - 20 Jul 2004