﻿id summary reporter owner description type status priority component severity resolution keywords cc release 1881 [PATCH] Pull projects list from the database mpalmer@… coderanger "As a sort-of followon from a previous ticket, I've modified the project index to consult the master environment's database of projects instead of just grovelling around on the filesystem. This is better because: * If you have a bunch of projects in some directory that ''don't'' go into the projects list (because they're not Tracforge projects), like I've got at the moment, the project index is noticably slower; * You can scatter your Trac projects hither and yon on the filesystem while still being able to get them all into the project index. [http://theshed.hezmatt.org/mattshacks/tracforge/_patches/bugfixes/20070802001456-6856b-6e77ed80dfc1eb7858fcd14637b1ba1a9211c10b.patch the patch] is a little ugly, since I couldn't work out how to get the master_env variable set correctly ''inside'' {{{_send_index}}} -- it would keep complaining about how objects of type {{{Option}}} or {{{EnvironmentOption}}} (depending on what I was trying to use at the time) lacked methods. Which is strange, because all I frigging wanted was a frigging '''string'''. Gah, Python confuses me." enhancement new normal TracForgePlugin normal 0.10