[IMP] Add the corresponding content type document instead the default content type
Raise exception when ir_attachment creation fails
yaml: use selected user and not admin for onchange

Fixes: #1885
yaml: use selected user and not admin for defaults
Raise exception, don't reraise it

Allow the traceback to show real origin instead of this line by calling `raise` instead of `raise e`
[FIX]product: add store=dict to field name_template

bzr revid: csn@openerp.com-20130412130856-3g5e67v2r7y6ep5v
[REF]product: remove one extra loop

bzr revid: csn@openerp.com-20130415102121-u74t7zd3zct3q3ts
[IMP] only recompute name_template if product_tmpl_id changes
PEP8
[MERGE] sale_order_dates: several improvements to usability and planned date computing, courtesy of Lionel Sausin (Numerigraphe)

bzr revid: odo@openerp.com-20140306202430-aw45sqw6og8ezcni
[FIX] sale_order_dates: fixes + deduplication of _get_planned_date()/_order_line_move_date() methods on sale.order

bzr revid: odo@openerp.com-20140306225009-f0jk43x5qpovurxi
[IMP] Add search filters in inventory analysis

Add search filters for products available, out of stock, and with negative stock in inventory analysis
improve looping efficiency
[IMP]: requested_date+commitment_date on quotation
Remove superfluous bracket for analytic account domain
Merge pull request #92 from mdietrichc2c/correct-invoice-line-domain

Remove superfluous bracket for analytic account domain
[FIX] account: do not duplicate analytic lines on analytic journal duplicate
[FIX] point_of_sale: fix point of sale sequence declaration, github issue #3218
Merge remote-tracking branch 'odoo/7.0' into 7.0
[FIX] mrp: perform location chaining for kit exploded moves

This rev. 7307227 ensured to not (re-)set the state 'confirmed' to exploded moves with a more advanced state (for instance, 'assigned')
Nevertheless, the location chaining is performed on the move confirmation, through the action_confirm method of the stock.move model. Besides, the resulting moves of the _action_explode method had the state 'confirmed' on creation, the 'confirmed' state wasn't set by the method 'action_confirm', meaning that the moves were confirmed without having the location chaining done. Allowing moves to go through the action_confirm method even if the state was 'confirmed' or further triggered the location chaining.

Preventing already confirmed moves to go through the action_confirm method prevented the location chaining, thus.

We now create the resulting moves with the 'draft' state, and then confirm them through the procurement workflow signal 'button_confirm'. Thus, the resulting moves are confirmed by going through the action_confirm method, writing the confirmed state and triggering the location chaining at the same time. We then write the 'assigned' state if necessary.

opw-617235