Just want to highlight, that base_contact is described explicitly in the new OpenERP book "Drive your Sales and Marketing" - Chapter 4.7 handed out during community days 2011, as alternate solution to manage contacts.
So problems ahead if this does not get fixed. regarding the usability / simplicity for those who do not need the full functionality of base_contact what about to have the infrastructur for base contact in place all the time and just povide 2 interfaces for the partner form * simplified = contact and address on one line. like with out base contact now * extended = like base_contact now -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/720935 Title: [6.0] base_contact install breaks function field res_user.user_email Status in OpenERP Modules (addons): Confirmed Bug description: this always returns the email of the last entered/updated user because of _email_set def _email_get(self, cr, uid, ids, name, arg, context=None): # perform this as superuser because the current user is allowed to read users, and that includes # the email, even without any direct read access on the res_partner_address object. return dict([(user.id, user.address_id.email) for user in self.browse(cr, 1, ids)]) # no context to avoid potential security issues as superuser one one hand this module covers basic needs but breaks essential functions of OpenERP _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
