Performance

Scrolling the home page is very slow

Sometimes scrolling the home page is really slow. This is probably because of the transparency of the menu. In future version of Tracks this will be fixed. In the mean time, you can remove transparency by removing in your standard.css all occurrences of:

filter: alpha(opacity=XX);

-moz-opacity: .XX;

opacity: .XX;

with XX being some value

Tracks on multiple screens (Linux)

A user of Tracks got big improvements by disabling Xinerama in X (he had dual screens). This was done by adding the following line to the “ServerLayout” section of /etc/X11/xorg.conf:

Option “Xinerama” “off”

Unfortunately, you can’t drag windows between the two screens now (they function as independent desktops instead).

Tracks 1.6

Some people are having problems (mostly under Safari, but also under Firefox) where contexts are collapsed and are unable to expand them. Deleting the Tracks cookie will expand all contexts (returning to default). See #727

Tracks 1.5trunk

Fix REST authentication with FastCGI (from Tommi Komulainen as posted on mailing list). “I was getting authentication failures when trying to use the REST API. Little investigation revealed it’s due to FastCGI and it can be resolved (or at least worked around) with the following line in .htaccess (Found from http://wiki.dreamhost.com/Ruby_on_Rails)”:


RewriteRule ^(.*)$ dispatch.fcgi [E=X_HTTP_AUTHORIZATION:%{http:AUTHORIZATION},QSA,L]


Tracks 1.04

1. If you’re using Safari, an error is generated if you try to add more than one next action in a row without refreshing the page. When the form is reset after submitting a next action, Safari wrongly sets the context_id option drop down to nil, which generates the error. Firefox and other browsers behave correctly. The work around is to select another context, then select the one you require before submitting the form for a second time. This sets context_id properly.


2. While viewing and navigation around Tracks works from a mobile phone browser, adding, deleting, editing and checking off next actions does not because of the limitations of Javascript in these browsers. We’re working on a mobile version which should solve these problems.

Installation with PostgreSQL

When Tracks is installed with PostgreSQL the todos table, done column is created as an integer by rake db_schema_import. However rails code tries to execute queries against this with ‘t’ and ‘f’ (true and false) which throws an exception. Altering this column to type of character with length 1 and default of ‘f’ seems to resolve the issue.

Migrating from MySQL to SQLite3 or vice-versa

Similar to the above, true values are stored as ‘t’ in sqlite3 and 1 in MySQL, and false as ‘f’ in sqlite3 and 0 in MySQL. So if you are migrating from one to the other, you will need to manually edit the values in your database before using the new database. Check for any boolean fields and alter the values as appropriate. There are several in the preferences table, the “hidden” field in the contexts table, and “is_admin” in the users table.