1. 23 Apr, 2016 2 commits
  2. 22 Apr, 2016 9 commits
  3. 21 Apr, 2016 10 commits
  4. 20 Apr, 2016 19 commits
    • Nicolas Martinelli's avatar
      [FIX] stock_landed_costs: fix the fix of the tests · 6a473e45
      Nicolas Martinelli authored
      Commit 6339bae8 fixes the tests, but now the tests are not testing
      what should be tested ;-)
      6a473e45
    • Christophe Simonis's avatar
      [FIX] stock_landed_costs: correct rounding tests · 6339bae8
      Christophe Simonis authored
      Previous forward-port (17b6191a) includes
      new tests (added by eb26694e) which are
      now broken because quants with a cost of zero are forbidden.
      
      Force a standard_price on created product to avoid this situation.
      Adapt quants cost values.
      
      Also change references of accounts and journals on records.
      6339bae8
    • Géry Debongnie's avatar
      [FIX] web: fix dataset to avoid race conditions · ab8a93c8
      Géry Debongnie authored
      The read_slice method in dataset is problematic, because it alters the
      dataset ids.  So, if 2 consecutive read_slice are started, but the first
      one ends after the second one, we don't have the correct ids in the
      dataset.
      
      This commit just make sure that previous read_slice do not alter the ids
      of the next read_slice.
      ab8a93c8
    • Géry Debongnie's avatar
      [REV] web_kanban: reverts 9b54b042 and 6859c8da · b8933420
      Géry Debongnie authored
      These 2 commits in kanban view fixed 1 bug by introducing a few other
      severe bugs. The tradeoff is not worth it, especially when it is
      balanced again deleting some contacts in your database.
      b8933420
    • Denis Ledoux's avatar
      [FIX] website_form: handle date & datetime · d5762302
      Denis Ledoux authored
      Adding date & datetime inputs in the website
      form builder couldn't work, because
      the posted values for these input
      types were not treated at all,
      and they were not in the format
      the date/datetime were stored in database.
      
      opw-672674
      d5762302
    • Christophe Simonis's avatar
    • Christophe Simonis's avatar
      ff3a7319
    • Christophe Simonis's avatar
      a255a6f6
    • Nicolas Martinelli's avatar
      [FIX] stock_landed_costs: precision · b112631b
      Nicolas Martinelli authored
      Oversight of commit bd025cda.
      I'm an idiot, I should have checked that another solution was applied
      from 9.0 with accounting refactoring. We apply it here as well.
      b112631b
    • Nicolas Martinelli's avatar
      [FIX] stock_landed_costs: account/valuation inconsistencies · eb26694e
      Nicolas Martinelli authored
      When stock landed costs are divided per product unit, inconsistencies
      may arise between the real stock valuation and the stock valuation
      account. This is likely to happen when several products are bought, but
      these products leave the stock one at a time.
      
      A numerical example is the following: a landed cost of 15.00 is applied
      to a purchase of 13 units. An amount of 15.00 is recorded when the
      products enter the stock. If the product leave the stock one at a time,
      13 entries of 1.15 are recorded (15.00/13 = 1.153846... ≈ 1.15), which
      is then equal to 13 * 1.15 = 14.95. In this case, All the products have
      left the stock (stock valuation is zero), but 5 cents remain on the
      account.
      
      This is of course even worse the higher the ratio is. For example, a
      landed cost of 4.00 split into 1000 units sold piece by piece will never
      be recorded when a product leaves the stock.
      
      The fix is to record the rounding difference on a specific quant. In the
      previous example, instead of adding 1.153846... on the unit cost of the
      13 units, we do the following:
      - 12 units to which we add 1.15 on unit cost
      - 1 unit to which we add 1.20 on unit cost
      
      opw-675222
      eb26694e
    • Nicolas Martinelli's avatar
      [FIX] stock_account: account/valuation inconsistencies · 262d98bb
      Nicolas Martinelli authored
      When the product price is divided per product unit, inconsistencies
      may arise between the real stock valuation and the stock valuation
      account. This is likely to happen when a product is bought in a UoM
      different from the standard UoM of the product.
      
      A numerical example is the following: a box of 13 is bought for 15.00.
      An amount of 15.00 is recorded when the products enter the stock. If the
      product leave the stock one at a time, 13 entries of 1.15 are recorded
      (15.00/13 = 1.153846... ≈ 1.15), which is then equal to
      13 * 1.15 = 14.95. In this case, All the products have left the stock
      (stock valuation is zero), but 5 cents remain on the account.
      
      This is of course even worse the higher the ratio is. For example, a
      box of 4.00 split into 1000 units sold piece by piece will never be
      recorded when a product leaves the stock.
      
      The fix is to record the rounding difference on a specific quant. In the
      previous example, instead of adding 1.153846... on the unit cost of the
      13 units, we do the following:
      - 12 units to which we add 1.15 on unit cost
      - 1 unit to which we add 1.20 on unit cost
      
      opw-675222
      262d98bb
    • Nicolas Martinelli's avatar
      [FIX] stock_landed_costs: former_cost_per_unit precision · bd025cda
      Nicolas Martinelli authored
      The precision of `former_cost_per_unit` should not be set. Indeed, a
      stock move can contain several quants with different unit prices.
      Therefore, we should not round the field when stored, otherwise the
      difference per unit will not be calculated correctly.
      
      This is a workaround since we cannot change the DB structure in stable.
      
      opw-675222
      bd025cda
    • Nicolas Martinelli's avatar
      [FIX] stock_landed_costs: use correct UoM · 85fd9721
      Nicolas Martinelli authored
      Use the normalized quantity, otherwise the amount per unit is wrongly
      calculated.
      85fd9721
    • Goffin Simon's avatar
      [FIX] account, l10n_generic_coa, l10n_th: U.S. CoA Misconfigured · 6f5acf60
      Goffin Simon authored
      Translation.
      
      opw:674632
      6f5acf60
    • Goffin Simon's avatar
      [FIX] l10n_generic_coa: · b8e73c24
      Goffin Simon authored
      The Cost of Good Sold should be of type "Direct Costs
      
      opw:674632
      b8e73c24
    • Olivier Dony's avatar
      [FIX] web: fix db manager layout in Chrome 50 · fc2aa736
      Olivier Dony authored
      Complement of f992c8ee,
      to be reverted in saas-6+ and in 8.0 when Chrome's
      fix reaches the stable Chrome channel.
      
      Fixes #11629
      
      See https://bugs.chromium.org/p/chromium/issues/detail?id=603507
      fc2aa736
    • Joren Van Onder's avatar
      [FIX] point_of_sale: display correct uom on weighable products · d043fd03
      Joren Van Onder authored
      Everything's displayed fine on orderlines with weighable products, this
      only affected the small blue labels on the products.
      
      opw-674264
      d043fd03
    • Denis Ledoux's avatar
      [FIX] sale: allow to import quotations without lines description · 5c476513
      Denis Ledoux authored
      When importing a quotation,
      if the lines `name`, `price_unit`, `product_uom` or `tax_id`
      are not specified, but the product is,
      retrieve them from the product `on_change`
      
      This was the case in Odoo 8.0,
      it was done as well in the override `create` method
      of `sale.order.line`
      
      opw-675434
      5c476513
    • Denis Ledoux's avatar
      [FIX] stock: remove spaces surrounding the `/` in locations complete name · 21ccf2fe
      Denis Ledoux authored
      The location name get is computed as:
      `parent.name + '/' + child.name`
      
      While, the complete was computed as:
      `parent.name + ' / ' + child.name`
      
      This leaded to an obvious inconsistency.
      
      Besides, this prevented to use the `location`
      filter in the search of the products list to
      know the quantity available of products for
      a specifc location, as the domain used
      to retrieve the locations is set as
      `[('complete_name','ilike',context['location'])]`
      
      `context['location']` containing the content of the `name_get`
      (No spaces surrounding `/`)
      and
      `complete_name` surrounding `/` with spaces.
      
      opw-674378
      21ccf2fe