Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #456 (closed defect: fixed)

Opened 13 years ago

Last modified 12 years ago

[SVN Rev. 579] KID templates can no longer extend sitetemplate.

Reported by: matt.bevan@… Owned by: anonymous
Priority: normal Milestone:
Component: TurboGears Version:
Severity: major Keywords:
Cc:

Description

Description

After updating to a fresh copy of the latest svn, 579, (by removing all existing TG-related packages and installing CherryPy? from SVN), sitetemplate is no longer processed and applied to KID templates.

Reproducing

  1. tg-admin quickstart a new package, say, 'testsite'.
  2. Start up the development site. You will see the welcome message with TurboGears cog at the bottom.
  3. Modify welcome.kid to import sitetemplate and extend sitetemplate.
  4. Modify master.kid to stand alone (do not import or extend anything).
  5. Modify the shiny new config.py to use "testsite.templates.master" as the sitetemplate.
  6. Re-launch the development site and refresh your web browser. The TurboGears graphic is gone - the sitetemplate is not used.

Change History

comment:1 Changed 13 years ago by matt.bevan@…

  • Component changed from Kid to TurboGears

I have further tracked the problem down to the new configuration system. Line 253 of view.py in the latest SVN (as of noon February 1st) never loads my custom configuration file. I suspect this has to do with other errors mentioned on the forums related to the new configuration system.

comment:2 Changed 13 years ago by kevin

I think this was actually broken by the template plugin system. What's going on here is that the plugin engine is being loaded (and configured!) when view.py is imported. It may be the case that this only happens if you have baseTemplates defined. I have moved loading of base templates to the server startup as of [616] to try to fix this.

comment:3 Changed 13 years ago by kevin

  • Status changed from new to closed
  • Resolution set to fixed

I think this was actually broken by the template plugin system. What's going on here is that the plugin engine is being loaded (and configured!) when view.py is imported. It may be the case that this only happens if you have baseTemplates defined. I have moved loading of base templates to the server startup as of [616] to try to fix this.

Note: See TracTickets for help on using tickets.