Doc enhancement: Reassure People They Didn't Lose Their Data
There are two well known ways that oops can come up through the user's browser problems. In these cases, all they have to do is hit "back". BUT they do have to read the message to find that out. New-time users need more reassurance....
--
MartinGregory - 05 Jul 2004
Follow up
These patches will cause the message to be more reassuring:
*** oopssave.tmpl~ 2004-04-22 01:48:43.000000000 +1000
--- oopssave.tmpl 2004-07-05 15:05:00.000000000 +1000
***************
*** 6,12 ****
You cannot call this script directly, %WIKITOOLNAME% uses it internally.
Some browser configurations occasionally send undefined data to the
! server. Don't worry, your changes are not lost. Just click the Back
button on your browser and then try Save again.
The other possibility is an internal error in %WIKITOOLNAME%
--- 6,12 ----
You cannot call this script directly, %WIKITOOLNAME% uses it internally.
Some browser configurations occasionally send undefined data to the
! server. <b>Don't worry, your changes are not lost.</b> Just click the Back
button on your browser and then try Save again.
The other possibility is an internal error in %WIKITOOLNAME%
*** oopsempty.tmpl~ 2004-07-05 15:18:36.000000000 +1000
--- oopsempty.tmpl 2004-07-05 15:03:47.000000000 +1000
***************
*** 6,12 ****
You cannot save a topic with no text entered. Please try again.
Some browser configurations occasionally send undefined data to the
! server. Don't worry, your changes are not lost. Just click the Back
button on your browser and try again.
The other possibility is that someone sent you the preview URL of
--- 6,12 ----
You cannot save a topic with no text entered. Please try again.
Some browser configurations occasionally send undefined data to the
! server. <b>Don't worry, your changes are not lost</b>. Just click the Back
button on your browser and try again.
The other possibility is that someone sent you the preview URL of
Fix record
commited to svn
--
SvenDowideit - 06 Jul 2004