## page was renamed from MoinMoinBugs/DataLossWhenPreviewingPagesWithIEinDesktopEditionMode ## page was renamed from MoinMoinBugs/SevereProblemsWhenPreviewingOrSavingPageWith1.7rc1inWindows = Description = I have just tested the new Moin 1.7rc01 and had severe trouble when previewing a page in IE (Moin run as desktop edition on WinXP Home Sp3): I edited a longer article thus pressed several times the preview button (every 5-10 minutes or so about 6-10 times). Suddenly when pressing the preview again, the editor closed, showed the normal page view and all the changes were lost. == Steps to reproduce == ## Describe the steps needed to reproduce the bug. If we can't reproduce it, we probably can't fix it. 1. Preview a page several times. == Example == ##Add URL that show the bug, screenshot or test wiki markup that fail... ##URL: ##attachment:screenshot.png ##{{{ ##Example wiki markup that fail ##}}} == Component selection == ## Where you think is this bug happening ? (general, plugin [plugin name], theme [theme name], ... * general == Details == ## If you got a traceback, please save the traceback page as html and attach here: ## attachment:traceback.html ## if the bug is in this wiki, just kill the table and write: This Wiki. ## If a traceback is not available, please fill in the details here: || '''!MoinMoin Version''' || Moin1.7rc1/rc2 || || '''OS and Version''' || Win XP Home SP3 / FAT32 / NTFS || || '''Python Version''' || Python 2.5 || || '''Server Setup''' || DesktopEdition || || '''Server Details''' || || || '''Browser''' || IE || || '''Language you are using the wiki in''' (set in the browser/UserPreferences) || Swabian || == Workaround == ## How to deal with the bug until it is fixed * use a sane browser like Firefox, Opera, ... * if you are forced to use IE, always mark all editor input and paste it to the clipboard. Then good luck: try to preview. = Discussion = I track Moin developpment since quite some time now. This behaviour is not unknown to me form earlier releases. However now it seems the have got worse. Is this again some caching problem?? Just tried rc2 as suggested: I have downloaded the tarball, extracted the files, ran wikiserver.py. I started to create a new page "!TestPage". I edited the page several minutes, hit preview about 6 or 7 times, then on the next hit the editor was closed and the page for a missing page appeared: "This page does not exist yet...". -- OliverSiemoneit <> Also "save changes" triggerd in the browser (IE) the browser's error page "Web page cannot be displayed" as in rc1. Something seems to be still broken. -- OliverSiemoneit <> Please try the same thing with another browser (like FF2). If it still misbehaves, try it on NTFS. Tried it now on Firefox 2.0.0.14 and Opera 9.27: It works fine! This seems to be a problem of IE7 only. That's a kind of strange.. -- OliverSiemoneit <> This problem may be related to MoinMoinBugs/GuiEditorPreviewDataLoss. My observation was that if the time between button (such as save changes, preview, etc.) presses was too short then the edit would be lost. The problem only occurred with IE. In Apache I changed the !KeepAliveTimeout to be smaller than the quickest time between two button presses and that appeared to fix the problem. A similar issue may be occurring here. -- JohnCarlson <> It would be interesting if it also happens on: * IE6 and moin 1.7.0rc2 * Happens also there. Brings up the browser's error page "Server not found" rather than showing the Moin page "This page does not exist yet. You can create...." as on IE7 * IE7 and moin 1.6.3 * Yes, it also happens there. Hitting "Preview" sometimes triggers two POST events in the console windows instead of only one. However the editor remains open. Sometimes these two POST events are followd by a new GET event, i.e. the editor is closed and all newly entered data is lost. /!\ After some hours of debugging and finding no reason at all for this sporadic IE misbehaviour, I decided not to continue wasting time trying to fix/workaround that. BTW, the internet is full of people trying to fix that without success and without much useful information. If you want it fixed, find someone else. Otherwise just use a browser that sucks less. -- ThomasWaldmann <> = Plan = ## This part is for Moin``Moin developers: * Priority: * Assigned to: * Status: won't fix, not a moin bug ---- ## If you are a moin core developer, replace the category to Category* in these cases: ## Category MoinMoinNoBug - if this is not a bug. ## Category MoinMoinBugConfirmed - if you can confirm the bug on current code. ## Category MoinMoinBugFixed - after the bug is fixed in current code. CategoryMoinMoinNoBug