On 12/28/05, Don Hopkins <[EMAIL PROTECTED]> wrote:
This is a bug in the patch that I submitted earlier and was applied today. The problem is that sitetemplate is in need of being refreshed, but because of the different way that it is loaded it seems to never be reloaded. I am working on a fix now. It should be ready shortly.
In development mode TurboGears calls kid.load_template which loads a file by path. The hex based module is how Kid handles loading by file path. In production mode the templates are imported so the names are more like what you would expect.
-- David
When I remove sitetemplate from the extension list of master.kid, everything works ok!Is sitetemplate necessary? Why isn't it reloading properly the second time it's reloaded (or third time it's displayed)?
This is a bug in the patch that I submitted earlier and was applied today. The problem is that sitetemplate is in need of being refreshed, but because of the different way that it is loaded it seems to never be reloaded. I am working on a fix now. It should be ready shortly.
Another thing I'm wondering about (that doesn't seem to be causing any errors, but mystifies me) is why are my master.kid and util.kid templates showing up in anonymous modules called ' kid.util.template_0xCE66A227L', instead of the expected "alive.alive.templates.master" and "alive.alive.templates.util"? Is it supposed to be like that? The __file__ names of these modules are correct, so it works ok, but I don't understand why the module names have random hex numbers in them.
In development mode TurboGears calls kid.load_template which loads a file by path. The hex based module is how Kid handles loading by file path. In production mode the templates are imported so the names are more like what you would expect.
-- David
