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 #1016 (closed defect: wontfix)

Opened 13 years ago

Last modified 12 years ago

Static-filter paths ignore server.webpath, disappear if path prepended

Reported by: acb@… Owned by: anonymous
Priority: normal Milestone: 1.5
Component: TurboGears Version: 0.9a6
Severity: major Keywords:


When a server.webpath argument is specified in the config file, to rebase a TurboGears application's URLs to /appname/, this does not apply to static directories; both those specified in the config file and those programmatically inserted (i.e., /tg_widgets) remain at /. Even worse, attempting to manually rebase the URLs, i.e., by replacing static with appname/static or hand-modifying cherrypy.config.configs, causes them to disappear.

This bug is making it impossible to deploy non-trivial TurboGears applications at a non-root path whilst using server.webpath. Please advise.

Change History

comment:1 Changed 13 years ago by elvelind

  • Component changed from CherryPy to TurboGears

comment:2 Changed 13 years ago by jorge.vargas

  • Type changed from defect to task
  • Milestone set to 1.1

static content is on the todo list.

comment:3 Changed 13 years ago by elvelind

  • Type changed from task to defect
  • Milestone changed from 1.1 to 1.0

This should be fixed before 1.0, even if the fix is a hack. In 1.1 webpath will no longer be needed when we switch to CP3.

comment:4 Changed 13 years ago by godoy

Agreed. If this can't be fixed, this possibility should be removed and the feature denied so that we don't have an inconsistent behavior between what we say we can do and what we can really do.

comment:5 Changed 12 years ago by alberto

  • Milestone changed from 1.0 to 1.1

comment:6 Changed 12 years ago by jorge.vargas

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

CP3 will be ported for 1.1 and this will no longer be needed

Note: See TracTickets for help on using tickets.