ToDo

Table of contents

• Ongoing issues
  • 1. Theme style
  • 2. Known bugs
  • 3. Roles
  • 4. Database Abstraction Layer
  • 5. Database Optimization
  • 6. More Usability and User friendly Interface
  • 7. Clean code
  • 8. Check issue with categories

Ongoing issues

1. Theme style

The current (as of Jan 13th, 2009) workspaces.css theme style (css and tpl) is not fully working nicely on a 2.x site. I tried making workspaces.css file import thenews.css, but the unfisnihed work is much more evident there. importing tikineat.css, everything seems to look like fine, as on Tiki 1.9.x. , or importing thenews.css in Tiki 2.x. Example of working scenarios:

• http://edu.tikiwiki.org (using tikipedia theme)
• http://www.ub.edu/optics/tiki (using eatlon theme)

2. Known bugs

Using AulaWiki 1.7.0 and Tiki 2.4:

• no calendars or structures can be created from the workspaces admin interface (they are not listed in the drop down).
• file galleries and image galleries are not being created (for me, at least), even if they are listed in the drop down of new resources to create in a previously created workspace. Reproduced in this site: http://www.ub.edu/optics/tiki
  • Quote:
    Our installation in our university uses php as cgi (not apache module).
    And the url of the server is something like:
    http://www2.ub.edu/optics/tiki (ftp uploading to the site www2.ub.edu), while the official url for visitors is http://www.ub.edu/optics/tiki
    
    So, after I click on the create resource (from the first domain), I'm directed to a wrong url (the second domain), by the way, saying that I don't have permission to see that resource, etc.. However, If I visit the right url, I can see that the resource has not been created.

3. Roles

There seems to a bug in roles in 1.6.2 version, which is fixed by pingus here if you change the files in here:
http://edu.tikiwiki.org/tiki-download_wiki_attachment.php?attId=21&page=ToDo
Fixed in 1.7.0?

4. Database Abstraction Layer

We need to provide an abstraction layer to the database because on next major release of TikiWiki (4.0), Workspaces will be included in it's core, and AulaWiki will not work with it's database tables (as a mod I say). So we need to make AulaWiki compatible with old versions and newer versions too.

5. Database Optimization

Until TikiWiki 4.0 will be ready to production, we need to perform a "boost" in the database tables to become more scalable for hundred of groups.

6. More Usability and User friendly Interface

Until now, to make a workspace available you need to perform some tasks, and it can be a little confusing. So I think it's a good idea to make more "simple" the interface allowing people to create his workspaces more easily and quickly.

7. Clean code

We need to clean all code as much as possible and generate documentation (very basic, of course)

8. Check issue with categories

See the report by pingus about the issue related to categories.
http://dev.tikiwiki.org/bug2297 : "another patch on aulawiki.1.6.2 for tikiwiki.2.2"

---