#12: Static content doesn't work for applications that are included in a larger
site
--------------------------------+-------------------------------------------
Reporter: kevin | Owner: anonymous
Type: defect | Status: new
Priority: highest | Milestone: __unclassified__
Component: TurboGears | Version: 0.9a6
Severity: normal | Resolution:
Keywords: needs confirmation |
--------------------------------+-------------------------------------------
Comment (by chrisz):
This problem appears with TG 1.x when you put you an app inside in a
namespace package, because the default app.cfg sets
{{{
[/static]
static_filter.on = True
static_filter.dir = "%(top_level_dir)s/static"
}}}
So the static directory (the same applies to `[/favicon.ico]`) is set to
the top level, i.e. the level of the namespace package instead of the
application which is one level deeper. We should add a comment to the
app.cfg file that in this case, you should use `package_dir` instead of
`top_level_dir`, or maybe even generally set
{{{
[/static]
static_filter.on = True
static_filter.dir = "%(package_dir)s/static"
}}}
See also
[http://groups.google.com/group/turbogears/browse_thread/thread/83c5b8547cf537f
here] in the mailing list.
--
Ticket URL: <http://trac.turbogears.org/ticket/12#comment:10>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
