Skip to content
Snippets Groups Projects
  1. Aug 01, 2019
    • wan's avatar
      [IMP] account: misc improvement post accountappocalypse · 81905658
      wan authored
      * remove _onchange_invoice_date_due as it is superseeded by _onchange_recompute_dynamic_lines
      * change invoice_date_due only if not set and if there is no payment term, it was erased and set to invoice_date_due if we did not set invoice_date_due before posting
      * raise a warning if we validate an empty move/invoice
      * correct the renaming of user_id -> invoice_user_id in invoice template
      * correct the renaming of date_invoice -> invoice_date
      * the data on purchase journals was not displayed correctly as the sign
      of the amount in the graphs was not signed correctly
      * the methods for computed invoice reference were not correctly renamed in l10n_be for (account.move)._get_invoice_computed_reference
      * the default reconciliation model was only installed in the first company, we make it now install along with the chart of account
      * the partner of invoices and the label of invoice lines should be required
      * the widget one2many_list doesn't exist
      
      closes odoo/odoo#34786
      
      Signed-off-by: default avatarCedric Snauwaert (csn) <csn@openerp.com>
      81905658
    • Sapan Zaveri's avatar
      [FIX] l10n_in, l10n_in_xx: load product demo in demo only · 1244dd0f
      Sapan Zaveri authored
      
      mistakenly product demo file load as real data
      
      bug introduced by this commit #8226b6d5c4b23f28e9f050b81ecdc2d26b9b6e6b
      
      task-2046174
      closes #34874
      
      Signed-off-by: default avatarJosse Colpaert <jco@openerp.com>
      1244dd0f
  2. Jul 30, 2019
  3. Jul 22, 2019
  4. Jul 25, 2019
    • Xavier Morel's avatar
      [FIX] core: auto_install modules being very sticky · fce64e7d
      Xavier Morel authored
      
      An unintended side-effect of #29431 is apparently that auto_install
      applications automatically get reinstalled when uninstalled, which was
      not the goal.
      
      Move the auto_install selection back into db.py, this version seems to
      work even though the previous attempt was apparently unsuccessful.
      
      closes odoo/odoo#35180
      
      Signed-off-by: default avatarXavier Morel (xmo) <xmo@odoo.com>
      fce64e7d
  5. Jul 26, 2019
  6. Jul 18, 2019
  7. Jul 26, 2019
  8. Jul 25, 2019
  9. Jul 24, 2019
    • Romain Derie's avatar
      [FIX] web_editor, website: avoid returning children of inactive view · 6a592240
      Romain Derie authored
      
      Before this commit, for the following view tree:
      P (active)
      |
      I (inactive)
      |
      II (active)
      When calling `get_related_views()` on 'P', it would wrongly return 'II'.
      It shouldn't, since its parent 'I' is inactive.
      
      Step to reproduce:
      - Go to /shop
      - Enable ecommerce categories
      - Enable Collapsible Cateogories
      - Disable ecommerce categories
      - Collapsible categories is still shown even if its parent got archived
      
      closes odoo/odoo#35154
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      6a592240
  10. Jul 25, 2019
    • Arnold Moyaux's avatar
      [FIX] stock: MTO overprocessed move · c8754185
      Arnold Moyaux authored
      
      Error due to other module (e.g. purchase_stock, mrp) that will
      define their own rules in order to merge or not moves together.
      Usecase:
      - Install purchase_stock
      - Create a product MTO + buy with a vendor
      - Create a SO of 1 unit
      - On the PO receive 2 units
      - On the delivery deliver 2 units
      
      It will create an empty delivery and put the entire move in
      a back order.
      
      First issue the extra move is created as a MTO if it's copied from an
      MTO move. So il will trigger all the pull rule. We won't it because it's
      an extra quantity and the rules should be only trigger by the original
      document (SO/MO).
      Also an extra move in a picking do the hypothesis that the original move and
      the extra move will always be merged together. But in the previous
      usecase, the module purchase add the condition that 'created_purchase_line_id'
      and 'purchase_line_id' should be the same in order to merge move.
      'created_purchase_line_id' is also copy=False, so the move and the
      extra move will not be merged. create_extra_move only returns the extra
      move and _action_done only process the moves returned by _create_extra_move.
      It result by an original move not merged and not processed by _action_done,
      it will be automaticaly set in a back order and the extra move is
      processed.
      
      In order to fix it, check if the move and the original move will be
      merged. If not, returns both moves.
      
      opw-2008113
      Close #34005
      
      closes odoo/odoo#34411
      
      Signed-off-by: default avatarSimon Lejeune (sle) <sle@openerp.com>
      c8754185
    • David Dufresne's avatar
      [CLA] signature for ddufresne · 5b80695f
      David Dufresne authored
      
      closes odoo/odoo#35079
      
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      5b80695f
  11. Jul 24, 2019
  12. Jul 23, 2019
  13. Jul 24, 2019
    • Jeremy Kersten's avatar
      [FIX] gamification: perf on write karma_min on gamification.karma.rank · 8a80efd7
      Jeremy Kersten authored
      
      This commits avoid to call recompute when you write on the rank without
      touch the karma_min value.
      
      On write on karma_min, we have 2 cases:
      - Rank order are the same, just need to recompute the rank for the user
      that could be impacted. Eg. if karma_min changes from 45 to 50, we need
      to recheck for all user between 45 and 50 their new rank.
      - Rank order are not the same, we need to recompute for all users.
      (could be still improved if needed)
      
      When you recompute the rank on a list of users, depending of the number of
      users (bulk if more than 3 * number of rank) we check for each user what is
      the new rank, or for each rank whats is the new users.
      
      task-internal
      
      No way to edit a rank on the prod server. Lock sql -> crash server
      
      closes odoo/odoo#34835
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      8a80efd7
Loading