parts.igem.org:Bug Reports:Archive

(Newest posts at bottom)
The following bug reports have been resolved and are now obsolete. Note that resolved bug reports will stay on the main page for at least a week so others can see the resolution. - Randy

  1. Reshma 14:56, 16 Nov 2005 (EST): The registry appears to have some strange behavior when you try to enter a feature is whose starting coordinate is greater than its ending coordinate. It highlights two small stretches of sequence. (I was doing this in an effort to see if I could indicate features on the opposite strand.)
    • Randy The code now detects this and complains. There is now an explicit direction for each feature.
  2. Reshma 14:56, 16 Nov 2005 (EST): When you add a feature that is only 1 nucleotide long (like a mutation). It highlights 4 bases in the sequence pane instead of 1.
    • BC 15:23, 8 Dec 2005 (EST): The same bug seems to occur for other small features. It seems to highlight not just 4 bases extra but everyting up to the next "gap" in the sequence display, i.e. up to the next multiple of 10. Based on a small sample size (B0036 in E7103 and I7102 and R0085)
    • Done - the new feature display does not have this bug - Randy
  3. Reshma 15:52, 16 Nov 2005 (EST): Somehow I am unable to edit the sequence of the part I just created (BBa_I50000). When I go to edit the sequence, it seems to just concatenate the sequence I type in rather than replacing the original sequence.
    • Done - This bug was a result of a browser limit on the length of a line in a text box. We now display sequences with limited line length. - Randy
  4. RS 15:15, 13 March 2006 (EST): The icon for primers doesn't show up in the deep component picture when primers are included as parts. Just a gap is shown.
    • Done - The icons have been added - Randy
  5. RS 15:48, 2 June 2006 (EDT): pSB5A5 doesn't have any information on it part main page even though it has [http://parts.mit.edu/d/parts/partsdb/part_info.cgi?part_name=pSB5A5 hard information].
    • Fixed with new release - Randy
  6. WingZero 21:50, 12 June 2006 (EDT): In MonoBook.css (the default stylesheet), there's a missing semicolon at the end of the line "padding-bottom: .17em" near the very end.
    • Fixed - Randy
  7. Rshetty 17:14, 1 June 2006 (EDT): Although CDS's in the reverse orientation now have their graphics displayed properly, -35 and -10 regions do not.
    • Fixed. But we may need direfctional icons for every part so it is easy to see if they are reversed. - Randy
  8. WingZero 20:59, 17 June 2006 (EDT): Pages like Add an Intermediate Part have TABLE tags with absolute widths. Whenever the browser window is resized, those sections tend to fall off the page (ie, outside the border from the Wiki software). On that page, at least, I don't really see the need for an absolute width (or even a table, for that matter; should be paragraph tags maybe).
    • R These pages are part of the database section of the Registry and share common formatting. This will not be changing soon.
  9. WingZero 16:44, 21 June 2006 (EDT): Maybe minor, maybe not, but pages like Search the Registry, DNA Part Repositories, and other CGI pages have 1) the wrong title (not a big deal) and 2) the top linkbar has the correct name, but the link always points to User:Randy (which may or may not be a security risk if we appear to be logged in as Randy).
  10. Scmohr 16:11, 15 February 2007 (EST): Also in the "Sequence and Features" boxes, the heading "Get selected sequence" is misplaced. It should be moved to one line above its present position.
    • Randy This bug has been fixed.
  11. Kahaynes 13:57, 3 February 2007 (EST): When I try to add a new composite part or construction intermediate, the site takes me back to the login page, even after I've logged in
    • Randy This bug has been fixed.
  12. Macowell 14:26, 15 February 2007 (EST): The Projects category on the Part Types page seems to be broken. It just displays: "There are no" and most of the usual mediawiki tabs like "edit" seem to be missing from the top of the page. NOTE: a similar error was reported earlier; see pre-upgrade entries 4. & 6.
    • Randy This bug has been fixed.