Luis, On 25 Aug 2008, at 8:18, Reinier Balt wrote:
>> >> the problem: no contexts show up on the home page. None of them. I've >> tried the following things so far to fix, neither worked: >> > > Did you compare the resulting database structure with the default > database > Structure from the tracks15-empty.db > Perhaps the script you used did not change everything? I'm thinking > of the > hide field of the context table. > > (please note that tracks15-empty needs a rake db:migrate, so you > won't find > the tables for recurring todos in there...) > >> * create a new context. Doesn't show up on the home page. >> * take an old context, set it to not visible, set it again to >> visible. >> Still doesn't show up on the home page. >> >> Almost everything else works fine: I can browse by project, context, >> and tickler, create new tasks (inc. recurring), edit or close old >> ones, etc. >> >> Two other things don't work, no idea if they might be related: >> * the mobile contexts page is empty > > This is most probably the same problem as above since the database > code is > shared between mobile and non-mobile view > >> * my primary user is no longer an admin (probably not related, not a >> big deal) >> > > Hmm, this could be related. Admin is a Boolean in the user table. > Perhaps > The booleans are not converted correctly I've seen these symptoms before with a conversion from MySQL to sqlite3, and in that case it was -- as Reinier suggests -- a problem with the boolean fields. MySQL uses 1/0 and sqlite3 uses t/f. Rails handles the interpretation of the field depending on the database connection type, but if it's expecting t/f and finds 1/0, things go wrong. I would use the sqlite3 command line tool to explore your database and check the value of the fields: > cd db > sqlite3 your-tracks-db.db sqlite> update contexts ...> set hide='f' ...> where hide=0; ...> select * from contexts; ...> .q You would do the converse and set hide='t' where hide=1 if you have any hidden contexts, along with any other boolean fields (there's 'done' in todos and couple of others, IIRC, so check the db schema. Then it should work OK. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
