I've been trying to find a way to show and manage attachments inside the form, rather than by using the 'attachment' menu button. The main reason is that I need to be able to manage attachments in sub-windows (without the menu buttons).

I've tried using fields.one2many but I keep getting exceptions.

I can also use fields.function to recreate the functionality, but that seems like re-inventing the wheel.

Any ideas anyone?

thanks.
Paul.

Hi pjstevns,

There shouldn't be a problem with o2m fields involving attachments. Can you post the relevant parts of your code?

(Also, note that there is already a menu action leading to the Attachment forms. It's located in 'Administration / Low Level Objects'.)

Thanks for replying.

I've been trying with code like this:



which doesn't work Wrong approach I assume.

The approach should work. Try putting domain restrictions in quotes, like this:

This should at least compile but may actually be insufficient to make the whole thing work. Did you add any XML to alter the view? Regarding the whole approach, did you hack into the distribution source code or did you derived a new model using OpenObject inheritance constructs?

I've constructed a custom object type that inherits directly from osv.osv. I need to be able to show attachments inside a form, because this class is only accessible from a sub-window.

I'm building a customization of project.project that refers to these realestate.property objects in a m2m relation. From the m2m widget you click on a realestate property that opens in a sub-window. Attachments are linked to these realestate properties, but the attachments button is not visible in these sub-windows - alas. If there's another module that does this, I can't find it despite extensive grepping of the code.

I started out with the quotes but noticed by scanning the openobject trunk source that other modules don't use quotes to pass a domain keyword argument to fields.many2many. I'm not sure it makes a difference.

Hi again pjstevns,


What exceptions do you get? By which component is it thrown (server, GTK client, Web client, Python interpreter)? Can you post all of your Python class for the inherited model? Also, I'm not sure why you first talked about a o2m relation and then switched to a m2m relation?

If you just want to add one field to an existing model, for such a simple customisation you may want to consider doing it directly from within the interface instead of developing a whole new module. If you only have a bunch a simple customisations, you can record and export them automatically in a module by installing the 'base_module_record' module.

Incase anyone is looking into this i got the same exceptions as well, coming from base.calendar function base_calendar_id2real_id
It looks like this line:
return base_calendar_id and int(base_calendar_id) or base_calendar_id
is breaking with the int part, basically the one2many relation is sending a [id] which isnt compatible with the int part of the expression. (Its saying it cant int a list object)
I managed to patch this by basically enclosing it in a try block:
try:
return base_calendar_id and int(base_calendar_id) or base_calendar_id
except Exception,e:
return base_calendar_id and base_calendar_id or base_calendar_id

Now the relation is working fine.
If anyone knows how to override that global function in base_calendar.py without having to modify that source file it would be useful,

Best Regards,
Mike

Further note, this only works if you want to look at attachments.
It doesnt seem to pass the res model through at all if your creating so:
To 'create' attachments from that view is a right pain, it wont seem to let me write to res_model in the default get so... Pass the context with the model through in the one to many xml (just put it as a string)
Then I created a new document class overridden from:
class document_file(osv.osv):
_inherit = 'ir.attachment'
def default_get(self, cr, user,fields_list=[], context=None):
#put code to check context is there etc
data['tmp_res_model']=str(context['res_model'])
return data
_columns = {
'tmp_res_model':fields.char('Res Model',size=256),
}

create an override view (Not sure if this part is necessary):
<record id="ir_attachment_model_inherit" model="ir.ui.view">
<field name="name">ir.attachment.model.form.inherit</field>
<field name="model">ir.attachment</field>
<field name="inherit_id" ref="document.view_document_file_form"/>
<field name="arch" type="xml">
<field name="user_id" position="after">
<field name="tmp_res_model" />
<newline/>
</field>
</field>
</record>

Then copy the create out of the document.py code...
def create(self, cr, uid, vals, context=None):
#all code here from document.py
then at end before cr.commit()
if(vals and 'tmp_res_model' in vals):
self.pool.get('ir.attachment').browse(cr,uid,result).write({'res_model':vals['tmp_res_model']})

NOW it will actually 'SAVE' documents using this view.