Important Issues

This is not a complete list of all known issues (for that, see the Open Issues page), but rather a grouping of the issues considered to be of greatest concern, and the detailing of any known workarounds.



Table of Contents

    Upgrade Issues
  1. Schema update for Tests&Quizzes (SAK-1321)
  2. CSS changes that may affect skins (SAK-1417)
  3. Samigo upgrade patch for MySQL (SAK-1356)
  4. 1.5 to 2.0 conversion script (SAK-1623)
    System Administration Issues
  1. DB tables grow without bound (SAK-1533)
  2. Tomcat does not shut down cleanly (SAK-1708)
    Functionality Issues
  1. WebDAV on the Mac (SAK-1306)
  2. Special characters in uploaded files prevents deletion (SAK-940)
  3. Confusing "Import File" link after site creation (SAK-1263)
  4. Tests&Quizzes default template does not allow edit of all possible settings (SAK-1659)
  5. MySQL UTF-8 encoding bug - breaks international characters (SAK-1737)

Upgrade Issues

  1. Schema update for Tests&Quizzes (SAK-1321)

    If you're running Oracle or are upgrading from a previous Sakai version you should check the datatype of the "MEDIA" column in the SAM_MEDIA_T table.

    The correct types for each database are:

    If you need to change this type for your database, this will also involve finding the primary key constraint, dropping it and then recreating it. Contact your local DBA for further information on making this change.

    Below is some sample Oracle SQLplus output to better illustrate (SYS_C0064435 is the example constraint; replace it with yours):

    SQL> alter table SAM_MEDIA_T modify MEDIA BLOB;

    Table altered.

    SQL> select constraint_name from user_constraints where table_name='SAM_MEDIA_T' and CONSTRAINT_TYPE='P';

    CONSTRAINT_NAME
    ------------------------------
    SYS_C0064435

    SQL> alter table sam_media_t drop constraint SYS_C0064435;

    Table altered.

    SQL> alter table SAM_MEDIA_T add constraint SYS_C0064435 primary key (MEDIAID);

    Table altered.

    SQL> desc SAM_MEDIA_T;

    [table with BLOB type]

    SQL> select constraint_name from user_constraints where table_name='SAM_MEDIA_T' and CONSTRAINT_TYPE='P';

    CONSTRAINT_NAME
    ------------------------------
    SYS_C0064435

    SQL> commit;

    Commit complete.

  2. CSS changes that may affect skins (SAK-1417

    The accessibility work for 2.0.1 included some changes to the portal.css and tool.css files:

    Both these changes were needed to make the portal easier to navigate with a screen reader. The default rendering of the h headers, whowever, would interfere with the sighted readers experience, so this issue was dealt with in the CSS, namely by:

    1. adding a class to the portal.css to render the <h1> off-screen (the <h1> are classed "skip"):
      .skip {
      position:absolute; top:-999px;
      left:-999px; height:0;width:0
      }

      The use of this selector in the portal also "hides" all the "jumpto" and "skipto" links and targets that have been added.

    2. addressing the <h2> in the tool titles contextually in the tool.css:

      .toolTitle td.title h2{
      font: normal bold 12px Arial, sans-serif;
      margin:0;
      padding:0;
      display:inline
      }
      Your own needs may dictate a different font, etc - the important thing is to override the default rendering of <h2>, and the padding and margin and "inline" definition are important in this regard.
  3. Samigo upgrade patch for MySQL (SAK-1356

    There is a Samigo patch for 2.0.0 databases that you should be aware of if you're not using a newly constituted 2.0.1 database.  This patch is available within the Jira item that describes it (http://bugs.sakaiproject.org/jira/browse/SAK-1356).  If you have an existing MySQL instance that you installed for sakai 2.0.0, please run the following script to update your existing tables.
    > mysql -u username -p schemaname < $HOME/sakai-src/sam/src/mysql/samigo-2.0.0.patch1.sql --force

    This will change the column type of date columns to 'datetime'.  Again, you should not run this script on a 2.0.1 (or otherwise patched) database.

  4. 1.5 to 2.0 DB conversion script (SAK-1623

    A script included with the source release will need to be run on a Sakai 1.5 DB to perform the schema alterations necessary for Sakai 2.0. You can find both Oracle and MySQL versions of this script in subversion (https://source.sakaiproject.org/svn/trunk/sakai/docs/).


System Administration Issues

  1. DB tables grow without bound (SAK-1533)

    Two tables - SAKAI_EVENT and SAKAI_SESSION - will grow at a rapid rate and without bound.  The workaround for 2.0.1 is to have these tables periodically cleaned out by a DBA or a cron job.  Below are sample SQL scripts for doing this in Oracle.  They may be easily altered appropriately for MySQL.  Consult your local DBA.

  2. Tomcat does not shut down cleanly (SAK-1708)

    If you're running James, you'll find that not all processes will stop when Tomcat is shut down.  Altering the James configuration is necessary to work around this for 2.0.1.

    The James configuration file is located at:

    legacy/james/src/webapp/apps/james/SAR-INF/config.xml

    Look for the section of the config file that looks like:

    <nntp-repository>
    [...]
    <spool>
    <configuration>
    <spoolPath>file://var/nntp/spool</spoolPath>
    <!-- The number of threads that process spooler related tasks. -->
    <threadCount>1</threadCount>
    <!-- The spool thread(s) should idle for some time, if it has nothing to do -->
    <threadIdleTime>60000</threadIdleTime>
    </configuration>
    </spool>
    </nntp-repository>

    and change the 'threadCount' value from 1 to 0. This should stop Tomcat from hanging upon shutdown.


Functionality Issues

  1. WebDAV on the Mac (SAK-1306)

    Some problems have been reported using the Goliath WebDAV client on the Mac. The native WebDAV client in Mac OS 10.4 (Tiger) does not appear to have these problems.

  2. Special characters in uploaded files prevents deletion (SAK-940)

    A small subset of characters are escaped in a non-standard way, and the consequence for Sakai is that uploaded resources with these characters in their filenames may not be able to be deleted or otherwise manipulated in the resources tool. This could be a significant issue, particularly for foreign language classes. The special characters include the carat (^), the question mark (?) and the semi-colon (;).

  3. Confusing "Import File" link upon site creation (SAK-1263)

    After creating a site, if you go to Site Info, you will see a new option: Import from File. The option doesn't seem to correspond with anything else that can be done in Sakai as a maintain user (meaning, there's no symmetrical "export to file", and the interface doesn't offer any clues as to what sort of file it wants).

    The sort of file that can be imported is an export performed by the Sakai Admin Archive tool or a special 'Export to Sakai' tool in Indiana University's OnCourse system.

  4. Tests&Quizzes default template does not allow edit of all possible settings (SAK-1659)

    The default template should allow assessment creators to view/edit all possible settings. Right now the default template only allows a few settings to be edited, and anyone who wants to adjust settings has to create their own template. This is essentially the workaround for 2.0.1: create a new template to gain access to all settings.

  5. MySQL UTF-8 encoding bug - breaks international characters (SAK-1737)

    For all releases of Sakai there is a bug appearing with MySQL where international characters are shown as ? instead of the original character. There are patches which can be applied to 2.0.x installations available in the Jira entry referenced above. Those patches can also be used as a pattern for fixing prior Sakai releases.