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 #12 (closed defect: fixed)

Opened 14 years ago

Last modified 10 years ago

Static content doesn't work for applications that are included in a larger site

Reported by: kevin Owned by: anonymous
Priority: low Milestone: 1.0.x bugfix
Component: TurboGears Version: 1.0.8
Severity: minor Keywords:


Since static files are configured in the config file, if they are included in an application that is joined up to form a larger site, the static files will not appear in the proper place beneath the application root.

Change History

comment:1 Changed 14 years ago by kevin

John Speno mentioned that the VirtualPathFilter? may help here.

comment:2 Changed 14 years ago by kevin

  • Priority changed from normal to highest

comment:3 Changed 14 years ago by fumanchu@…

This is probably fixed in CherryPy? changeset  760, which allows arbitrary mount points using a  VirtualPathFilter.

comment:4 Changed 13 years ago by anonymous

  • Milestone set to 1.1

comment:5 Changed 13 years ago by godoy

Kevin, did r760 fix this? I saw you talking to somebody about a new approach for First Class, but is it OK for what we have in the trunk?

comment:6 Changed 12 years ago by jorge.vargas

  • Component changed from TurboGears to CherryPy

with the move for CP3 this should become obsolete.

comment:7 Changed 12 years ago by alberto

  • Milestone changed from 1.1 to __unclassified__

Batch moved into unclassified from 1.1 to properly track progress on the later

comment:8 Changed 11 years ago by Chris Arndt

  • Keywords needs confirmation added
  • Component changed from CherryPy to TurboGears

comment:9 Changed 11 years ago by lszyba1

How are you including the static content? For example if you are mounting you application via a modwsgi then all url and static request would have SCRIPT_NAME appended to them.

This tickiet #2033 makes sure that all urls are encoded with tg.url('someurl') by default in tg2 quickstart and therefore they should be properly mounted via modwsgi.

So the question for this bug would be how do you include your application in larger site? It should work with modwsgi.

comment:10 Changed 10 years ago 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_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_filter.on = True
static_filter.dir = "%(package_dir)s/static"

See also  here in the mailing list.

comment:11 Changed 10 years ago by chrisz

  • Status changed from new to closed
  • Severity changed from normal to minor
  • Priority changed from highest to low
  • Version changed from 0.9a6 to 1.0.8
  • Milestone changed from __unclassified__ to 1.0.x bugfix
  • Keywords needs confirmation removed
  • Resolution set to fixed

To finally close this matter, changed the app.cfg as suggested in r6168. Also adapted the online docs accordingly and explained the difference between top_level_dir and package_dir. Since this can be considered a bug, and since it cannot break existing TG 1.0 applications, committed this to the 1.0.x bugfix branch as well.

Note: See TracTickets for help on using tickets.