- Sep 11, 2015
-
-
Simon Lejeune authored
-
Simon Lejeune authored
-
Simon Lejeune authored
-
Olivier Dony authored
-
qsm-odoo authored
Tag template data were wrong since many2manytag color introduction
-
Yannick Tivisse authored
-
Yannick Tivisse authored
And why the hell are these many2many fields called tax_id and taxes_id
-
Yannick Tivisse authored
the product is not stockable
-
Yannick Tivisse authored
-
Yannick Tivisse authored
-
qsm-odoo authored
CSS to LESS Adaptation to new webclient
-
qsm-odoo authored
-
qsm-odoo authored
-
qsm-odoo authored
* Missing oe_title * Wrong indentation
-
Nicolas Martinelli authored
Since it is possible to select several SO and generate the invoices at once, it must be possible to view all these generated invoices.
-
Nicolas Martinelli authored
Due to new Sale module
-
Josse Colpaert authored
-
Simon Lejeune authored
-
Richard Mathot authored
It allows people to only use the rating service of the sales orders
-
Chirag Dodiya authored
-
Olivier Dony authored
QWeb's LazyResponse mechanism allows controllers to be inherited and to alter the rendering context (qwebcontext) *after* calling super(). However it caused the final rendering to occur outside the protection of the @service.model.check decorator that handles concurrent access errors. In rare cases the lazy rendering can be interrupted by a concurrent access error, for example when bootstrapping the the cache of asset bundles (as it INSERTs a bunch of attachments). By forcing the flatten()ing of the lazy response earlier, right after calling the route's endpoint(), it occurs within the protection of the @service.model.check, and benefits from the automatic retry. flatten() was modified to avoid rendering twice the template The flatten() in get_response() is still necessary for addons code that directly calls get_response(). Moved QWebException into openerp.exceptions next to the other exceptions classes - since it now has more global semantics. ~ The whole request dispatching code could really do with a complete redesign/simplification.
-
Josse Colpaert authored
-
Josse Colpaert authored
-
Arthur Maniet authored
-
Arthur Maniet authored
-
Arthur Maniet authored
Make all common form operations doable through barcode scanning
-
Arthur Maniet authored
Since the method must return a deferred, resolve it with true to proceed with onchange and with false to prevent the onchange. Deferred failure is not an option.
-
Nicolas Martinelli authored
For some reason, the computed Many2many or One2many field is not received through the onchange RPC call when creating a new order, but only once the order is saved. This makes the widget displaying previous orders kind of useless. We use this workaround with the default value in order to be sure to send the value in the default_get call. We also display previous orders and the agressive alerts in edit mode.
-
Nicolas Martinelli authored
-
qsm-odoo authored
In some cases, saving the formview when a listview editable line was being edited forced the line changes to be discarded.
-
qsm-odoo authored
-
qsm-odoo authored
-
Rakesh Sindhav authored
-
Josse Colpaert authored
[IMP] stock: product form Forecast statbutton with incoming/outgoing qty and product template and product product should be the same and consistent The button Inventory Adjustement is also changed to Update Qty On Hand as an inventory adjustment would expect a total inventory. These buttons do not need a variant security group. The incoming and outgoing quantity give more information on the forecast button immediately. The stock move view (Traceability statbutton) should not allow for creating or editing immediately.
-
Christophe Matthieu authored
-
Christophe Matthieu authored
-
Christophe Matthieu authored
Use convert_to_cache and convert_to_read to format onchange values. Fix: default value can be a command list, the onchange convert the comand list into a wrong comand list of command list.
-
Christophe Matthieu authored
-
Raphael Collet authored
-
Olivier Dony authored
-