mass_editing: Avoid errors if 'model_id' is not a list of ids.#325
Conversation
|
Hey @hpestano, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
|
Can you please explain your use case (steps to reproduce the error on the UI)? You need also to send the CLA |
|
La Habana, 2016-01-07
I hereby agree to the terms of the Odoo Individual Contributor License
Agreement v1.0.
I declare that I am authorized and able to make this agreement and sign this
declaration.
Signed,
Henrik Pestano Pino hpestano@gmail.com https://github.com/hpestano
|
|
The error is to make a search in the model 'ir.model.fields' My goal is to get ids fields 'res.partner' but the addon mass_editing overwrites the search function in IrModelFields. When I run the query |
|
Hi @pedrobaeza, I'm a coworker with @hpestano. The point of this change is that without mass_editing installed a query like: works out of the box. However, after installing mass_editing it fails cause it changes the I'm working with @hpestano so that he signs the CLA and send it and also we're gonna rebase this change on top of 8.0. Best regards, |
Without 'mass_editing' installed you can search the 'ir.model.fields'
like this:
ir_model_fields.search([('model_id', '=', 'res.partner')])
and it works.
However mass_editing changes the 'search' method and broke this type
of query. This commit fixes the 'search' method so that it allows the
legacy behavior.
Closes OCA#325 for a new PR.
Without 'mass_editing' installed you can search the 'ir.model.fields'
like this:
ir_model_fields.search([('model_id', '=', 'res.partner')])
and it works.
However mass_editing changes the 'search' method and broke this type
of query. This commit fixes the 'search' method so that it allows the
legacy behavior.
Closes OCA#325 for a new PR.
|
@lasley, why did you merge it so fast? We haven't even checked the CLA. |
|
Wait what? This is the first I've seen of this PR, I don't even see how I could have accidentally merged it. The merge itself only contains translations too, none of which was included in the commits in this PR, so I'm thoroughly confused 1861b63 |
|
So uhhhh how do we fix this? |
|
No, it seems that you haven't do anything. It has been auto-merged as they have make an strange GIT operation, resulting this PR in 0 commits. No worry then. |
|
I wonder why it marked me as the merger though, that's weird. I guess this is why I sign my commits - maybe should start doing it on merges too in hindsight |
|
I think it could happen because you have pushed a branch to GitHub that contains same commits, and detect this one as the same with commit history, and interpreted it as it was merged. But nothing to do with the signing of the commits. |
|
Hi @pedrobaeza, Indeed we reset our 8.0 branch to match that of OCA and created another branch with the patch (now PR #638). This seems to have confused github somehow. Sorry for the inconvenience. |
|
The problem is that you used here the |
|
@mvaled - FYI the commits you made on this fix are now gone, but still recoverable. I recommend you make a new branch, cherry pick 86dc30f & 6168a48, and submit a new PR (assuming you want to continue forward with the changes). You will also need to sign the CLA & send to cla@odoo-community.org |
|
@lasley I did that already. Now is PR #638. I have personally signed the CLA, but since this change comes from my team, I've just sent the CLA for our organization https://github.com/merchise-autrement. Best regards, |
…mpty-field 8.0 web widget one2many tags empty field
Syncing from upstream OCA/server-tools (8.0)
When I try to make this query
I get this error
That is why i suggest this change