View source for Bug Reports 2009 - 2013

[[Image:Bugs.png|left ]]

<strike>
'''A creepy old friend ...''' 
Open token tabs are still bugged - '''You can neither save them nor provide global tags for them'''.

We are working on the problem, but until further notice: '''DO NOT WORK WITH TOKEN TABS'''

[[[[User:Dorothee|Dorothee]] 14:43, 12 March 2009 (CET)]]

[[Image:Bugs.png|left]]                                                                                                                                                                                                                   
   '''The most annoying bug is the following: When one annotates it makes a lot of sense to keep taps of the most recently annotated
    '''tokens. However, as soon as one has one token-tap open, the second token one opens cannot be saved anymore. Even if one now
    '''starts to close all previously opened token-taps, it remains impossible to save the token that one just had worked on. :( '''
   ([[User:Dorothee|Dorothee]] 17:21, 20 December 2008 (CET))                                        
 [[Image:Bugs.png|left ]][[Image:Bugs.png|left ]]

  '''Bugs creeping in with the Lazy Annotation''' 
   This bug is new and came with the Lazy Annotation Mode: it seems as if saving is not always possible - it is kind of off and on.
   As was reported to me from one of the TypeCraft classes connected to a course at Dragvoll saving was not possible until the LAM-button was 
   unmarked. Then saving was possible again. Sorry nothing reproducible yet ([[User:Dorothee|Dorothee]] 18:00, 27 November 2008 (CET)) :(
   
   I started to work on a long sentence and tried to add construction tags, but could not use that functionality. Pressed button *CHANGE* for 
   construction parameters, but nothing happened, then I also noticed that I cannot save the sentence. That was on the day LAM was introduced. Have not
   encountered that bug again ([[User:Dorothee|Dorothee]] 18:00, 27 November 2008 (CET))

   I guess there was some cook-up having to do with the change of domain that we did around the same time. 
   Yet there is a real bug which arises when one opens a certain number of token tags under annotation. It is only possible to save changes to
   the '''last token that was opened'''. In addition one cannot open the *Change* button that allows one to specify the construction type parameters.
   ([[User:Dorothee|Dorothee]] 16:55, 15 December 2008 (CET))

</strike>

Fixed as of today, [[[[User:Pavel|Pavel]] 11:18, 24 March 2009 (EET)]]


<strike>            
 '''The Bug List'''
   1. Oh my, long phrases imported from the database into the wiki 'run' out off the browser
      window. They trail off to the right. :(
      Is there anything that can be done about that?? You can see what we mean by looking at 
      [[Documenting Lule Sami]]. 
      Well ok, it is not a bug really but it looks so incredibly ugly :( 
</strike>
      
'''This has been fixed!''' Really long sentences now look as they should. Look at the German sentence below. --[[User:Dorothee|Dorothee]] 15:57, 2 July 2009 (CEST)


<Phrase>8694</Phrase>

<strike>
   2. In (1) below '''<:CASE>''' IS coming ''before'' the '''ILL-SG'''. Better is:    '''ILL.SG ''' (Kristin)
      Within the tier annotation of a TCtoken <:CASE> should not appear at all! It is meant as an indication of the grammatical category to
      which the tag belongs. Information like ''acc<:CASE'' should only be available under mousing over tags
      ([[User:Dorothee|Dorothee]] 12:05, 15 December 2008 (CET))
</strike>

<strike>
   3. ([[User:Ben|Ben]] 07 Apr 2009)  
      Deleting an unsaved text results in user-level error message "Text id cannot be null". 
      Message should be more user-friendly (or dropped entirely).
</strike> Message dropped and text gets "deleted" as any other text.

   4. ([[User:Ben|Ben]] 07 Apr 2009)  
      Newly instantiated phrases are not saved immediately (after navigating through the "TypeCraft wants to know" box).

<strike>
   5. ([[User:Ben|Ben]] 07 Apr 2009)
      Clicking OK in the "TypeCraft wants to know" box when instantiating a phrase results in an empty phrase table.
      (BMW: have fix)
</strike> Fixed

<strike>
   6. ([[User:Ben|Ben]] 07 Apr 2009)
      It is not possible to delete the final lone word in a phrase table.
</strike> By design, fixed minor bug showing in Firebug and added a user-friendly message

<strike>
   7. ([[User:Ben|Ben]] 07 Apr 2009)
      Phrase tabs in text editor remain after phrase has been deleted.
</strike> Fixed, they close now

<strike>
   8. ([[User:Ben|Ben]] 07 Apr 2009)
      "Search for phrases" with "Look only within phrases I can edit" checked: Java error "unexpected end of subtree".
      (BMW: have fix)
</strike> Fixed

   9. ([[User:Ben|Ben]] 07 Apr 2009)
      Not a real bug, but annoying. Clicking on a text found via "Search for texts" opens the text in a NEW tab.
      I would much prefer the text to open up in the current frame.

<strike>
   10. ([[User:Ben|Ben]] 07 Apr 2009)
       "Search for phrases" with "Constr. description" instantiated: Java error 
       caused by "java.sql.SQLException: Column not found: CONSTRUCTIONDESCRIPTION"
       (BMW: have fix)
</strike> Fixed

   11. ([[User:Ben|Ben]] 07 Apr 2009)
       When using LabelConventions tagset in "Search for phrases", the interface appears to be confused.
       Eg. Constituent Property appears thrice, only one choice is available for Situation Type, ...

This is not a code bug but rather a bad tag set. Should be fixed by whoever entered it into the database.

<strike>
   12. ([[User:Ben|Ben]] 17 Apr 2009)
       Attempts to set "Publish text" to false are ignored.
       (BMW: have fix)
</strike> Fixed

==Standalone Client==

Please report bugs in the '''standalone client''' here.