Description

A single user is getting systematic traceback when trying to save a page. Both IE and Firefox have shown this problem. It does not seem to be link to a particular page being edited, but rather to a specific user.

Steps to reproduce

It was possible to reproduce this by making a copy of the user Home page and Home/MoinEditorBackup to another user name and trying to edit a page with that user account.

Example

• Traceback: http://tigreraye.org/error.html

• UserName/MoinEditorBackup: http://tigreraye.org/moineditor.tar.bz2

Details

Workaround

Looks like a broken page. cd data/pages/PageName ; mv current-locked current

• I've tried:

   cd data/pages/PageName(2f)MoinEditorBackup
   mv current-locked current

  => which did nothing (sorry, I read the suggested fix too quickly).

• I then did:

   cd data/pages/
   rm -rf PageName(2f)MoinEditorBackup

  which worked.

Discussion

I have seen this error before, it happens while testing broken code. The user editor backup page get broken and then you can't save until you remove the editor backup. The reason for this is unclear, and I never saw it with working code.

Since its very rare, fix in later release. -- NirSoffer 2005-02-11 00:03:56

There is some finally: in PageEditor.py (in function _write_file - with stuff indented by 8 blanks btw.) - wasnt that the proposed solution to this bug? Maybe it is better to change this in 1.5beta, when we have less conflicts and more time. -- ThomasWaldmann 2005-07-30 13:15:45

• I added it, yes. Let us see if this mitigates the bug. In the end, we should use locks that can be broken. -- AlexanderSchremmer 2005-07-31 11:54:51

Plan

• Priority: Low
• Assigned to:
• Status: Fixed in 1.3.5

CategoryMoinMoinBugFixed