Skip to content
Snippets Groups Projects
  1. Nov 09, 2017
  2. Nov 08, 2017
  3. Nov 07, 2017
    • Jeremy Kersten's avatar
      [FIX] hr_timesheet_sheet: avoid ambigous field action in sql. · 15715e82
      Jeremy Kersten authored
      ERROR: column reference "action" is ambiguous
      
      This commit closes #13839
      15715e82
    • Nicolas Martinelli's avatar
      [FIX] crm: default user when copy · 3b43ddd2
      Nicolas Martinelli authored
      - Create a user A
      - Create a lead, assign to A
      - Deactivate user A
      - Duplicate the lead
      
      A notification email is sent to A (user assigned to the lead).
      
      Since the user is archived, he should not receive any email since it
      might contain sensitive information.
      
      opw-778825
      3b43ddd2
    • Nicolas Seinlet's avatar
      Backport 2d66d9a6 · 6488682c
      Nicolas Seinlet authored
      [FIX] *: do not use groups when extending an asset bundle
      Using groups when declaring an extension of an asset bundle leads to a
      different generated asset bundle according to the user's group. This
      is not something we want because a dynamic asset bundle's content
      means that it could (and it does) trigger unwanted cache invalidation.
      
      website_event, website_blog, website_forum and website_sale add
      functions to . These functions are bound to
      server side qweb nodes protected by groups. We can always add the
      functions; if a user tries to use the routes he should receive a
      traceback because of lack of access rules
      
      website_blog adds a  module, but is guarded by
      the presence of a node in the DOM. We use the same logic to guard the
      module added by website_sale with the  node.
      
      website_gengo is working as expected.
      6488682c
  4. Nov 06, 2017
  5. Nov 05, 2017
  6. Nov 03, 2017
  7. Nov 02, 2017
  8. Oct 31, 2017
    • Richard Mathot's avatar
      [FIX] l10n_br: wrong & pointless field redefinition · b9b6deff
      Richard Mathot authored
      Fields `amount_type` on `account.tax` and `account.tax.template` are
      already defined in the `account` module.
      Redefining them here (with the same parameters) breaks every other
      module that would have used `selection_add=` on those fields.
      
      Actually, it is the case in `account_tax_python`, and thus, all the
      localizations/customizations that depend on it were broken by this one.
      
      ~ Old API backport of 5d0d80af ~
      b9b6deff
    • Stefan Rijnhart's avatar
      [FIX] l10n_br: wrong & pointless field redefinition · 5d0d80af
      Stefan Rijnhart authored
      Fields `amount_type` on `account.tax` and `account.tax.template` are
      already defined in the `account` module.
      Redefining them here (with the same parameters) breaks every other
      module that would have used `selection_add=` on those fields.
      
      Actually, it is the case in `account_tax_python`, and thus, all the
      localizations/customizations that depend on it were broken by this one.
      
      (issue spotted by 11.0-nightly)
      
      Closes #19812 #20596
      5d0d80af
    • Christophe Simonis's avatar
      a0157f10
Loading