Hi, Am Donnerstag, 9. März 2017, 19:22:36 CEST schrieb Cédric Krier: > > The strange thing is, that it does not work anymore if i update a > > completely independent module. For example: > > 1. everything is working all right > > 2. i update stock_lot with the client interface > > 3. the prices in the product are grayed out and show the prices of the > > template > > 4. i restart the server > > 5. eyerything works fine again > > Humm, it is more and more interesting. > I think the problem relies in the fact that when updating the pool call > __setup__ after each module but when started normally the __setup__ is > only called once. > So the _no_template_field is not always filled when __setup__ is called. > But normally the Product.__setup__ should not override existing field. > > By the way, you do not need to your fields in _no_template_field, this > is only for field that should not be duplicate are not defined on > Product.
Got the same problem. It seems what happens is when updating, Product.__setup__ is called before the __setup__ in the custom module had a chance to manipulate _no_template_field. Also, at this moment, the fields of the custom module are not registered yet, so the check if the field is already existing fails, and the field is copied. Seems to be a genuine bug. mfg Robert -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/1991979.pLPBzCC8sZ%40smaug.
