#222 Reload after disable debug mode


WoaS 0.12.0 Prev. 12 with FF 3.6.3

I've edited a fresh WoaS-File (new pages). Then in Special::Options I deactivated "Enable debug mode and debug console (requires Woas reload)" and pressed "Save optons".
After reload by browser-button my new pages were disappeared.
Reproducible (changes of the current session get lost).


  • Daniel

    Daniel - 2010-06-13

    I cannot reproduce this bug; when I add new pages, they are saved to disk and they become permanent

  • Daniel

    Daniel - 2010-06-13
    • assigned_to: nobody --> legolas558
    • status: open --> pending-works-for-me
  • mk-berlin

    mk-berlin - 2010-06-13

    Deeper tests show:
    independently of a changed option, the button "Save options" saves the wiki without previously made changes in existing pages, without contents of new pages, only the new pagenames are saved. Further editing will save the correct wiki, but closing the browser or pressing the browser-reload-button immediately after "Save options" will cause loss of data.
    Error exists at least since 0.11.9, and 0.12.0 Prev. 10 shows:
    "WoaS Unhandled errorr ---- FATAL: data arrays have mismatching length! #pages =71, #page_attrs = 71, #page_titles = 72, #pae_mts =71 [[OK]]"
    (FF 3.6.3 Win XP)

  • mk-berlin

    mk-berlin - 2010-06-13
    • status: pending-works-for-me --> open-works-for-me
  • Daniel

    Daniel - 2010-06-14

    Can you specify the browser that you are using?

  • mk-berlin

    mk-berlin - 2010-06-14

    I use Firefox 3.6.3.on Windows XP SP3.
    Same effects with Internetexplorer 6.0 and 7.0.

  • PVHL (Paul)

    PVHL (Paul) - 2010-12-30
    • priority: 5 --> 9
    • labels: 1377984 --> Save feature
    • status: open-works-for-me --> open
  • PVHL (Paul)

    PVHL (Paul) - 2010-12-30

    Daniele, this is, in fact, a bug. It is somewhat difficult to describe what's happening in a few words. My woas-fix version fixes it by disabling partial save, so that an option change must save the whole file.

    A full save saves everything out to a file. The new file is not reloaded; this is not a problem. A partial save saves only changes out to the file by using whatever it finds in innerHTML. Given that inner HTML contains the old stuff that was loaded, not the new changes that are only in the Javascript VM, any changes made are lost. Obviously, this is only an issue when using the single-file version.

    It is possible this is different on some browsers, but this is how it is working on Firefox in Windows and Linux. The easiest way for me to


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks