Re: [pylons-discuss] context, mako and nivecms

2013-12-19 Thread Bert JW Regeer
Ah, I see one is in value, the other in system. Sorry. I don’t know how nive works, why can’t you pass in nive_context instead of context in the first place? Bert On Dec 19, 2013, at 12:03, wilk wrote: > On 19-12-2013, Bert JW Regeer wrote: >> When and where is this nive context passed to Mak

[pylons-discuss] Re: context, mako and nivecms

2013-12-19 Thread wilk
On 19-12-2013, Bert JW Regeer wrote: > When and where is this nive context passed to Mako? > > Do note that the sample code you added is the same as the one for the > Pyramid context (not request) so it won’t work. You can’t have two > variables named context passed into a renderer… I did exactl

Re: [pylons-discuss] context, mako and nivecms

2013-12-19 Thread Bert JW Regeer
When and where is this nive context passed to Mako? Do note that the sample code you added is the same as the one for the Pyramid context (not request) so it won’t work. You can’t have two variables named context passed into a renderer… On Dec 19, 2013, at 5:55, wilk wrote: > Hi, > > I try t

[pylons-discuss] context, mako and nivecms

2013-12-19 Thread wilk
Hi, I try to use mako template with nive_cms, but they both use "context", so mako complain that it's a reserved name... NameConflictError: Reserved words passed to render(): context I've seen in pyramid_mako there is already a workaround to rename pyramid request to _request : context = syste