In formalchemy/ext/pylons/, with pylons version > 0.7 I suggest to use named route to define "static_contents" route

[GoogleCodeExporter]

Hi,

In formalchemy/ext/pylons/, with pylons version > 0.7 I suggest to use
named route to define "static_contents" route :

map.connect('static_contents', '%s/static_contents/{id}' % url,
controller=controller, action='static')

instead of :

map.connect('%s/static_contents/{id}' % url, controller=controller,
action='static')

then we can use 

url_for('static_contents', id='admin.css')}}

which is cleaner than :

url_for(modelname='static_contents', action='admin.css', id=None)

Now, I can't change template for backward compatibility.

Original issue reported on code.google.com by klein.stephane on 16 Feb 2009 at 12:13

Attachments:

• static_contents.patch

[GoogleCodeExporter]

is this work with old pylons versions ? at least 0.9.6

Original comment by gael.pas...@gmail.com on 20 Feb 2009 at 12:04

[GoogleCodeExporter]

0.9.6 does support named routes, although you'd need to use the old :id instead 
of {id}

Original comment by jbel...@gmail.com on 28 Feb 2009 at 1:44

[GoogleCodeExporter]

so feel free to apply your patch but also change this for the old routes style

Original comment by gael.pas...@gmail.com on 12 Mar 2009 at 10:45

• Changed state: Accepted