From b3c0d126e9dfece1e52bc7f0ae5de91383aa538d Mon Sep 17 00:00:00 2001
From: Olivier Dony <odo@openerp.com>
Date: Mon, 12 Mar 2012 11:20:01 +0100
Subject: [PATCH] [FIX] project: project preference field must be editable

The user preferences screen is kind of a hack
because it lets the user modify fields on a
model that is normally read-only for her (res.users).
This is accomplished by a custom write() method
on res.users combined with a view on which some
fields are forced to be read-write using a
trick: @readonly=0.

bzr revid: odo@openerp.com-20120312102001-aas39wknhsyxkhbx
---
 addons/project/project_view.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/addons/project/project_view.xml b/addons/project/project_view.xml
index 26abe86fe99..d2740ce4992 100644
--- a/addons/project/project_view.xml
+++ b/addons/project/project_view.xml
@@ -676,7 +676,7 @@
          <field eval="18" name="priority"/>
          <field name="arch" type="xml">
             <group name="default_filters" position="inside">
-                <field name="context_project_id" context="{'user_preference':True}" widget="selection"/>
+                <field name="context_project_id" context="{'user_preference':True}" widget="selection" readonly="0"/>
             </group>
        </field>
     </record>