The issue is now solved in unstable build 20120520 ( http://unstable.tg.gy/20120520/index/ ).
The issue was caused by the fact that TurboGears doesn't permit to register more than one engine for content type. As both mako and genshi were registered the last registered one (in this case genshi) was the used one, being it available in your application or not. Now when multiple template engines are @exposed TurboGears will only register engines which are listed in your application renderers and will always prefer the one which is registered as the default_renderer in your application. Upgrading the TurboGears2 package is required to fix it. On Sun, May 20, 2012 at 2:47 PM, Alessandro Molina <[email protected]> wrote: > Hi Moritz, > thanks for the feedback. > > I'm not a mako user myself so I didn't find the issue, I'll give a > check as soon as possible and push a new unstable release. > TG 2.2 now quickstarts all the projects adding the genshi template > support by default even thought you choose a different template engine > to solve those kind of problems, but as tgext.crud was meant to work > with mako too it should work even without genshi. > > On Sun, May 20, 2012 at 12:00 PM, Moritz Schlarb <[email protected]> > wrote: >> HI Alessandro, >> >> this is just a partial feedback for tgext.crud: >> Since I'm currently overwriting the mount_point myself, I wanted to update >> tgext.crud from 0.5 to 0.5.1 but that gives me a >> MissingRendererError: The renderer for 'genshi' templates is missing. >> (since I'm using mako, I haven't registered genshi as renderer). >> Is that caused by the explicit renderer names since Changeset 35cd3ca7b24f >> or is it something in Turbogears 2.2 that is different from 2.1.5? >> >> Regards, >> Moritz >> >> Am Freitag, 18. Mai 2012 18:08:50 UTC+2 schrieb Alessandro Molina: >>> >>> As 2.2 release is going to introduce many big changes we want to be >>> sure that everything works as expected before making an official >>> release. >>> >>> To achieve this we decided to have some beta releases which will >>> permit people to start testing things and report issues found before >>> the stable release. >>> To perform the previous Beta release, Michael did all the full release >>> steps that would be done during a stable release. >>> As this is a slow process it would not permit to achieve the fastest >>> release cycle an unstable release needs. >>> >>> To speed up unstable releases http://unstable.tg.gy/ has been created, >>> that is based on an automatic release script that packages everything >>> up and creates a new release whenever a breakpoint is reached. All the >>> previous unstable releases keep being available and can be installed >>> in any moment. >>> >>> People that want to try the upcoming 2.2 and give help reporting >>> issues can create a new virtual environment following the instructions >>> available at http://unstable.tg.gy/. >>> The documentation for the last unstable release is available at >>> http://unstable.tg.gy/docs/ >>> >>> The changes between the previous 2.2 beta are: >>> - Twitter Bootstrap based quickstart >>> - Kajiki and Jinja quickstarts >>> - Easier Authentication and Authorization setup (removed repoze.what >>> dependency) >>> - Sprox 0.8b included, now it is possible to use admin with ToscaWidgets2 >>> - tgext.crud now uses only relative urls to work correctly with >>> controllers returned by _lookup >>> - Mako now uses auto_reload_templates option like all the other >>> template engines instead of its own templating.mako.reloadfromdisk >>> - __before__ and __after__ got removed as they were deprecated >>> - Jinja templates now use .jinja extension by default to avoid >>> messing with genshi templates >>> - use_legacy_renderer option got removed as it was deprecated >>> - tg.url method now accepts the qualified=True option to create full >>> qualified urls >>> - Passing arguments to tg.url to add parameters to the url got >>> removed as it was deprecated (use params=dict() syntax) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TurboGears" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/turbogears/-/1vj9ykOpzXMJ. >> 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?hl=en. -- You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en.
