As suspected it is an issue related to new tw2.core templates lookup. It is trying to render the widget template as a Jinja one even though it is a genshi one.
The issue is caused by the fact that .html is a valid extension for both Jinja and genshi templates in tw2 and as your project is using Jinja it favorites Jinja and ends trying to render a Genshi template as a Jinja one. I'll look for a fix with Toscawidgets guys as soon as possible and roll out a new unstable release in a few hours. Thanks for your report. On Thu, Jun 14, 2012 at 10:43 PM, Alessandro Molina <[email protected]> wrote: > Thank you for your report, not being a Jinja user I missed it. > It might have something to do with the recent changes in how tw.core > handles template engines, I'll give a look right now. > > On Thu, Jun 14, 2012 at 11:16 AM, Arthur Gavkaliuk <[email protected]> > wrote: >> Hello >> I've started new project with 20120607 build and choose jinja2 as >> default template engine. >> When I'm going to admin of any model I see source of genshi call >> instead of rendered widget - http://owely.com/4105VY8 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TurboGears Trunk" 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/turbogears-trunk?hl=en. >> -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en.
