If you edit a file and you don't have write access to that file,
it will give you the edit screen anyway.
Then when you go to save, you get the "oopssave.tmpl" message
which is totally confusing since it says "Save used incorrectly".
On my installation, I've changed the "oopsave.tmpl" to say:
Probably you did not have write access to the directory or file
that was being edited. The other possibility is an internal error in TWiki configuration.
The real solution is for the "edit" operation to fail immediately
if the ,v file can't be written.
Separate issue: I get this same "Save used improperly" error all the time using codev at Sourceforge. When I do the preview and save again, it works for some reason. This may be due to some internal delay between the machine running perl and the file server.
--
StanleyKnutson - 29 Nov 2000
Is this error related to
BetterErrorHandlingOnTopicSave?
I see these types of errors a lot with the Dec 2000 version of TWiki I've installed on a couple of servers. I also see it on the TWiki.org site.
In fact, I saw the error when editing this very page. I bounced back and forth between the preview and error screen a few times. Then, in a separate window, I edited the
BetterErrorHandlingOnTopicSave topic. Then I came back here and tried again, and it worked. So maybe it's a timing issue?
--
KristopherJohnson - 12 Apr 2001
Error handling has been improved in the 01 Sep 2001 release.
No check is done however by the time you edit a topic if the directory is writable. This is an installation issue, not a user permission issue.
--
PeterThoeny - 04 Dec 2001