Another issue... If you check the change log I linked to in my previous message the newest message for 1.12.3 talks about another bug with SCRIPT_NAME and the singleton keyword. That was the solution to another problem I had a while ago...if I remember right.
-Dave On Jul 13, 8:36 pm, David Hoese <[email protected]> wrote: > I had a similar problem earlier this year. What exact version of > Routes do you have? Routes 1.12.2 fixed this issue (newest release is > 1.12.3). > > From change log athttp://routes.groovie.org/changes.html: > Fix bug with routes URLGenerator not properly including SCRIPT_NAME > when generating qualified URL’s. > > Update your Routes and it should work. Hope this helps. > > -Dave > > On Jul 12, 9:33 pm, Way Chuang Ang <[email protected]> wrote: > > > > > > > > > Hi fellow pylons masters, > > > I encounter a problem as described in the subject of the mail. I > > integrated pylons applications into apache webserver using mod_wsgi. > > The configuration for wsgi is as such: > > > WSGIScriptAlias /mtrace /var/lib/lgmtrace/lgmtrace.wsgi > > > However, using h.url_for within the mako template doesn't yield proper > > url for static internal route as described > > inhttp://pylonsbook.com/en/1.1/urls-routing-and-dispatch.html#internal-.... > > I've checked the environment variable in the BaseController of pylons > > and SCRIPT_NAME has been properly set to /mtrace. > > > So, I decided to look into the code of url_for function within the > > routes package. As it turns out, environ attribute was never set for > > config variables returned from request_config. As a result, the code > > that calls for config.environ.get('SCRIPT_NAME') was never executed. > > > I wonder if anyone can help me on this matter because I'm stucked on > > this problem for quite some time already. Has anyone faces the same > > situation? How to fix it so that the URL can be resolved correctly. I > > couldn't find any results for my problem on google and stackoverflow, > > so I guess it must be some sort of configuration error that leads to > > this situation. For your information, I use all the default packages > > provided by Fedora 14 for mod_wsgi (3.2.2), apache server (2.2.17), > > pylons (1.0), routes (1.12). > > > Thank you. > > > Regards, > > Ang Way Chuang -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
