View source for Open bugs

Wandora is developed actively. We know the software is incomplete and absolutely contains bugs. This page documents some obvious bugs in Wandora. The list is updated frequently. Wandora contains also some peculiar features that may look like bugs. See [[FAQ for Wandora user]] for a list of such features.

* There is currently a known bug with [[Linked topic map]]s. If you reconfigure a layer that is being used by a linked topic map, the linked topic map will in some cases go to an unusable state. This happens if the reconfigured layer is a database topic map, query topic map or another linked topic. Reconfiguring here means right clicking the layer in the layer tree and selecting ''Configure layer''. To work around this bug, you must delete and recreate any linked topic maps that point to a layer that you need to reconfigure, if the layer contains one of the topic map types listed above.
* Wandora's internal topic map schema changed a little on update dated March 4, 2008. Subject identifier base of schema topics changed to '''http://www.wandora.org'''. It used to be '''http://www.wandora.net''' in previous Wandora releases! This change may cause problems while working with old Wandora projects as Wandora doesn't find important topics such as '''Wandora class''', '''Wandora language''', and '''Wandora language name version'''. To fix the problem you can either
** Add new subject identifier to schema topics with URI base '''http://www.wandora.org'''.
** Use regular expression replacer to change the SI base path '''http://www.wandora.net''' to '''http://www.wandora.org'''.

* The logging pop-up generates sometimes NullPointerException. This bug has no effect on Wandora except annoying exception report to the shell console window (which is invisible if you started Wandora with '''Wandora.exe''').
* Sometimes topic tree gets messy. To fix the problem you can choose to Fresh topic tree or reopen the topic tree component.


== Resolving problems and reporting bugs ==

If you encounter problems using Wandora

* Save your current project and close Wandora.
* Start Wandora with shell scripts found in '''bin''' folder. '''Wandora.bat''' is the default script you might want to try first. if you have a feeling that the problem was caused by insufficient memory you can also try '''Wandora-large.bat''' or '''Wandora-huge.bat'''. Starting Wandora with the script opens a shell window beside the Wandora window. Wandora writes extra logs to the shell window.
* Load your project back to Wandora.
* Repeat the action producing problems.
* Check the console shell window. If shell window contains suspicious text fragments such as Java exceptions please copy the text and send it to us by email to {{wandora email address}} and we'll try to fix the problem. Please remember to attach general description of the action producing errors. Also include '''[Wandora]''' to your email title. This ensures your valuable report is not trashed by our spam filter. You may also report the bug in [http://www.wandora.net/wandora/forum/index.php Wandora forum].