Context is not defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
New
|
Undecided
|
OpenERP Publisher's Warranty Team |
Bug Description
when adding to a window action a domain value that contains a context.get() it trows the following traceback:
2013-12-13 16:49:46,841 12533 ERROR clean openerp.netsvc: name 'context' is not defined
Traceback (most recent call last):
File "/home/
result = ExportService.
File "/home/
res = fn(db, uid, *params)
File "/home/
return self.execute(db, uid, obj, method, *args, **kw or {})
File "/home/
return f(self, dbname, *args, **kwargs)
File "/home/
res = self.execute_cr(cr, uid, obj, method, *args, **kw)
File "/home/
return getattr(object, method)(cr, uid, *args, **kw)
File "/home/
dom = menu.action.domain and eval(menu.
File "/home/
return eval(test_
File "", line 1, in <module>
NameError: name 'context' is not defined
the weird thing is that the domain filtering works properly, but always displays this error message.
test scenario:
Activate developer mode.
go to Project > Tasks > then edit the window action
in the field domain add this [('user_
context variable is supposed to be allways present in OpenERP but it is not working in this action in particular.
Thanks in advance
=======
Forgot to say that I also tested on runbot at the moment I posted this bug getting the same odd result.
description: | updated |
Changed in openobject-server: | |
assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
tags: | added: maintenance |
using context.get('uid') was just an example because I knew you can replicate the error with this value, I'm using a special value in the context not the uid, but anyway, the traceback says: id','=' ,context. get('uid' ))] and it works like magic, no error shown, can this be an addons bug instead of a openerp-server bug?
NameError: name 'context' is not defined
IMHO this should not happen, because is saying that it cant find the variable context, another weird thing is that this issue only happens on the example posted on the bug (the Tasks action), tried on the res.partner action the exact same domain [('user_