Skip to content
Snippets Groups Projects
  1. Oct 11, 2019
  2. Oct 10, 2019
  3. Oct 11, 2019
    • fw-bot's avatar
      [FIX] web: use language week_start in datepickers · eeb51831
      fw-bot authored
      
      Before this rev., if the week_start param (the first day of week)
      of the user language was changed, it wasn't reflected on datepickers
      (however, it worked fine in the calendar view). This rev. makes this
      work by updating the moment locale with the corresponding param.
      
      Fixes #36450
      Closes #36532
      
      closes odoo/odoo#38398
      
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      eeb51831
  4. Oct 10, 2019
    • jbm-odoo's avatar
      [FIX] web: List editable top select last row · 996f77b0
      jbm-odoo authored
      
      Before this commit, when we have a list (editable top) in a form
      with some mandatory fields and some existing rows. If we click on
      'add a line', a new empty line appear on the top, then we click on
      the last row, the empty row will disappear and we will have a
      traceback.
      
      After this commit, if we repeat this scenario, we click on the last
      row, we will be able to edit this last row.
      
      closes odoo/odoo#38302
      
      Signed-off-by: default avatarVincentSchippefilt <VincentSchippefilt@users.noreply.github.com>
      996f77b0
  5. Oct 09, 2019
  6. Oct 10, 2019
    • Pedro M. Baeza's avatar
      [IMP] purchase: Take into account purchase order date for sequence · ce423e6a
      Pedro M. Baeza authored
      
      **Steps to reproduce**
      
      * Define "Purchase Order" sequence for using date ranges checking "Use subsequences per date_range".
      * Change sequence prefix to "PO/%(year)s/".
      * Create a purchase order with order date in 2020 (a different year than current one).
      
      **Current behavior**
      
      Got a purchase order with 2019 (current year) number.
      
      **Expected behavior**
      
      Got a purchase order with 2020 number.
      
      closes odoo/odoo#37762
      
      Signed-off-by: default avatarDamien Bouvy (dbo) <dbo@odoo.com>
      ce423e6a
    • Pedro M. Baeza's avatar
      [IMP] sale: Take into account sales order date for sequence · 20baf00d
      Pedro M. Baeza authored
      **Steps to reproduce**
      
      * Define "Sales Order" sequence for using date ranges checking "Use subsequences per date_range".
      * Change sequence prefix to "SO/%(year)s/".
      * Create a sales order with order date in 2020 (a different year than current one).
      
      **Current behavior**
      
      Got a sales order with 2019 (current year) number.
      
      **Expected behavior**
      
      Got a sales order with 2020 number.
      20baf00d
    • fw-bot's avatar
      [FIX] l10n_mx: Transition Tax Accounts must be reconcilable · 3a4d8475
      fw-bot authored
      This issue is relevant for MX Localization because Cash Basis is created
      with the rate of the payment, and not with the rate of the invoice as is
      done for odoo core.
      
      closes odoo/odoo#38386
      
      X-original-commit: 10bb81c8
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      3a4d8475
    • Antoine Prieels's avatar
      [FIX] pos_hr: res.users loaded twice · 26274dbb
      Antoine Prieels authored
      
      When pos_hr was installed, `load_models` was called twice for res.users
      and calls to `load_fields` were not processed correctly.
      
      closes odoo/odoo#38374
      
      Signed-off-by: default avatarpimodoo <pimodoo@users.noreply.github.com>
      26274dbb
    • Antoine Prieels's avatar
      [FIX] point_of_sale: Scrollbar on receipt print · 84418ae5
      Antoine Prieels authored
      A scrollbar appeared every time a receipt was printed. To fix this,
      we put a height of 0 to the div that contains the receipt.
      
      html2canvas then had trouble computing the height of the background.
      There's a `height` option that can be given to the library but if the
      logo on the receipt was not loaded yet, the size we computed was wrong.
      We then compute the height only once the images have been loaded, in
      the `onparsed` method.
      
      We also remove a CSS class that wasn't used anymore.
      84418ae5
    • Nans Lefebvre's avatar
      [FIX] website: fix _update_visitor_last_visit concurrency issues · cc88a367
      Nans Lefebvre authored
      
      Install the website, install a second language.
      Switch the language on the website: error 500.
      
      The function opened a new cursor, to update website_visitor.
      It did so at the end of the query dispatch.
      However when switching the language of the website, the lang is written on the
      website visitor. This is done at the flush, done at the end (exit) of the query.
      This is done on the cursor that was used for all the transaction.
      Therefore that write would systemically fail on a
      ERROR: could not serialize access due to concurrent update
      
      opw 2080986
      
      closes odoo/odoo#38372
      
      Signed-off-by: default avatarNans Lefebvre (len) <len@odoo.com>
      cc88a367
  7. Oct 11, 2019
  8. Oct 10, 2019
  9. Oct 09, 2019
  10. Oct 10, 2019
  11. Oct 07, 2019
  12. Oct 08, 2019
  13. Oct 10, 2019
  14. Oct 08, 2019
  15. Sep 24, 2019
    • jbm-odoo's avatar
      [IMP] web calendar: Keep width box while drag or resize · 40529460
      jbm-odoo authored
      
      When there are many events at the same moment in a calendar,
      events are thin and on mouse hover the event take all the width.
      
      Before this commit, when we drag or we resize a event in calendar,
      the event returns to the state thin.
      
      After this commit, the width event stay width during resizing and
      draging.
      
      closes odoo/odoo#37334
      
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      40529460
  16. Oct 08, 2019
    • Nans Lefebvre's avatar
      [FIX] account: round debit and credit of account move lines at creation · 93789337
      Nans Lefebvre authored
      
      This fix is similar to 80200333; both are workarounds for the bug (limitation)
      introduced by 9d87d15d.
      In this case, the currency_field is a related field, and these fields are only
      computed after scalar values are written in database.
      As a result, this value is not rounded at creation.
      
      It is a problem since typically accounting reports are written directly in SQL,
      and thus reuse the values directly.
      Anyway even in the ORM the convert_to_cache optimised this away using the
      assumption that 'the value should have been rounded in convert_to_column'.
      It follows that in the report, errors can be accumulated
      to the point where the report is not balanced.
      This needs to be fixed in database by going through every existing line.
      
      Of note: the limitation that was readily acknowledged has not been worked around
      anywhere, in fact almost every single currency_field is a related one.
      Also of note, commit afef71d6 should "Always round monetary values in database"
      while it explicitly checked for the presence of the currency_field in the values
      and while not introducing a mechanism to make sure it would always be in the
      values.
      
      opw 2066849
      
      closes odoo/odoo#38341
      
      Signed-off-by: default avatarNans Lefebvre (len) <len@odoo.com>
      93789337
  17. Oct 10, 2019
  18. Oct 09, 2019
  19. Oct 08, 2019
Loading