Skip to content
Snippets Groups Projects
  1. Sep 30, 2019
  2. Oct 01, 2019
  3. Sep 30, 2019
  4. Sep 23, 2019
  5. Sep 18, 2019
  6. Sep 12, 2019
  7. Sep 13, 2019
    • len-odoo's avatar
      [FIX] mail: do not have _get_message_needaction crash on empty task list · 52526920
      len-odoo authored
      
      Suppose that a Task is added on a task via a studio customisation.
      Then the _get_message_needaction method gets called on the onchange of the
      toplevel task, which triggers another call to _get_message_needaction.
      During that update, we get a self with a model.newID; its ids field is empty,
      so the list of tasks res itself is empty.
      As a result the method crashes on a malformed query.
      This can in turn prevent the completion of some higher-level operation,
      e.g. a state change on the task.
      
      opw 1909043
      
      closes odoo/odoo#29084
      
      closes odoo/odoo#36813
      
      Signed-off-by: default avatarNans Lefebvre (len) <len@odoo.com>
      52526920
  8. Sep 11, 2019
    • Jairo Llopis's avatar
      [FIX] *: remove buggy calls to with_context · 921f5ffd
      Jairo Llopis authored
      
      When .with_context() is called with a dictionary as 1st positional
      argument, it will replace context (and not modify the referenced keys)
      It may create bugs when losing the content of the context (e.g. remove
      partner's language)
      
      This is a partial backport of #36164 with the website part as
      discussed.
      
      closes odoo/odoo#36692
      
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      921f5ffd
  9. Sep 10, 2019
  10. Sep 01, 2019
  11. Aug 29, 2019
  12. Jul 09, 2019
    • Jairo Llopis's avatar
      [FIX] auth_oauth: Override qcontext in the right place · 7c99310b
      Jairo Llopis authored
      
      Before this patch, if some module was based on top of `auth_signup`, and `auth_oauth` was also installed in the same database, the only way to get the proper qcontext would be to call `super()` inside `web_auth_signup_qcontext`, which would produce a login, which is most likely not desired because such addon would try to add some logic on top of it that maybe prevents login based on some circumstances.
      
      After this patch, any submodules can work properly without workarounds.
      
      closes odoo/odoo#34690
      
      Signed-off-by: default avatarChristophe Simonis <chs@odoo.com>
      7c99310b
  13. Aug 28, 2019
  14. Aug 22, 2019
    • Nicolas Lempereur's avatar
      [FIX] web_editor: parallax effect in sanitized field · da474d0e
      Nicolas Lempereur authored
      
      A sanitize fields by default remove all attributes outside of a
      whitelist (if sanitize_attributes on field is not set to false).
      
      This prevent to use parallax widget in Html sanitized field since
      attribute "data-scroll-background-ratio" define parallax effect speed
      but was not in whitelist.
      
      note: also keep data-interval for gallery widget
      
      opw-2053983
      closes #35961
      
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      da474d0e
  15. Aug 21, 2019
  16. Aug 20, 2019
  17. Aug 12, 2019
    • Raphael Collet's avatar
      [FIX] field: compute transitive dependencies over non-stored fields · 59c59cd8
      Raphael Collet authored
      
      In other words, when a field F depends on a non-stored field G, it also depends
      on G's dependencies.  This guarantees that whenever a dependency of G is
      modified, F will be invalidated and marked to recompute (if necessary).
      
      The transitive closure of dependencies is not computed over stored fields.
      Anyway stored fields already trigger the recomputation of their dependent
      fields during their recomputation.  The performance impact on the loading of a
      registry is negligible (less than 1%), and the increase of recomputation
      triggers is small (less than 10%).
      
      (cherry picked from commit 3fbd86bc)
      
      opw-2033493
      
      closes odoo/odoo#35636
      
      Signed-off-by: default avatarRaphael Collet (rco) <rco@openerp.com>
      59c59cd8
  18. Aug 14, 2019
    • Abridbus's avatar
      [FIX] mail: removing whitespace on message_id from incoming mail · 2fc46a06
      Abridbus authored
      
      Because of a whitespace character present at the beginning of the message_id of some mails,
      they were fetched twice.
      
      From the SQL side, we see that Outlook is formatting the header following the RFC822
      by allowing the header to look like:
      
      Header:<CRLF>
      <whitespace><hash_of_msg_id>
      
      From RFC822:
      "Each header field can be viewed as a single, logical line of ASCII characters.
      For convenience, the field-body portion of this conceptual entity can be split
      into a multiple-line representation" (abr.)
      
      It was also possible to find out by checking the logs.
      One or two whitespace(s) can be seen before the hash of the msg_id.
      
      The following commit is making sure we use and save the message_id without the whitespace
      by stripping them off on the coming mail.
      
      OPW-2006806
      
      Applying CHS solution to avoid crash on empty header.
      
      closes odoo/odoo#35682
      
      Signed-off-by: default avatarbve-odoo <Abridbus@users.noreply.github.com>
      2fc46a06
  19. Jul 29, 2019
    • amoyaux's avatar
      [FIX] stock : webplanner link to product does not work. · af3f6e59
      amoyaux authored
      
      In the planner the url are generated by prepare_backend_url that takes
      an action's xml id as argument. The id passed should have the format
      'module_name_where_the_action_is.action_name'. In this case the id passed
      was product.product_template_action_product but the action is defined in
      stock thus the prepare_backend_url was not able to find the associate action
      and return a wrong(default) url.
      
      This commit change the action id passed with the correct module.
      
      closes odoo/odoo#18812
      
      Signed-off-by: default avatarArnold Moyaux <amoyaux@users.noreply.github.com>
      af3f6e59
  20. Aug 01, 2019
  21. Jul 30, 2019
  22. Jul 29, 2019
  23. Jul 25, 2019
  24. Jul 24, 2019
    • Romain Derie's avatar
      [FIX] web_editor, website: avoid returning children of inactive view · cb3bf550
      Romain Derie authored
      
      Before this commit, for the following view tree:
      P (active)
      |
      I (inactive)
      |
      II (active)
      When calling `customize_template_get()` 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
      
      Test writen in 12.0 with #35154
      
      closes odoo/odoo#35155
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      cb3bf550
  25. Jul 16, 2019
    • Damien Bouvy's avatar
      [FIX] payment_authorize: md5 to sha512 compat · f7b6d3b0
      Damien Bouvy authored
      
      This commit extends the changes introduced by 88de9311 to adapt
      Odoo payment flows to the switch in transaction signature done
      by Authorize.net.
      
      The initial fix was not sufficient for flows that mixed redirection
      payment flows and server-to-server flows (e.g. paying a quote with a
      card that gets saved then using the token to pay for a subscription).
      
      The problem comes from the fact that the server-to-server API uses
      the API Transaction Key and API Login ID as credentials to authenticate
      requests; there is no need for a signature since this data is never
      publicly exposed on the website and a MITM is mitigated by the fact
      that it would need to be done between the Odoo server and the
      Authorize.net servers (both of which use https in a normal deployment)
      which is admitedly more complex than doing a MITM on a Starbucks wifi.
      
      On the other hand, the 'redirection' flow will include all transaction
      parameters as inputs in an html form, therefore the signature is
      required to ensure that the values have not been modified by a website
      user or a mitm.
      
      Since both flows can coexist on the same configuration, we cannot use
      the same field depending on the payment flow configuration - we need
      both fields to be stored for the provider.
      
      This commit therefore has to introduce new fields on payment.acquirer
      record that can store the signature key for authorize in addition to the
      usual authorize fields. Instead of adding a new module, this commit uses
      non-stored computed fields that will generate System Parameters entries
      for any acquirer of the 'authorize' kind when set through the interface.
      
      closes odoo/odoo#34670
      
      Signed-off-by: default avatarDamien Bouvy (dbo) <dbo@odoo.com>
      f7b6d3b0
  26. Jul 17, 2019
  27. Jul 10, 2019
    • Goffin Simon's avatar
      [FIX] account: Incorrect due date for credit notes · bb712ad7
      Goffin Simon authored
      
      Steps to reproduce the bug:
      
      - Create an invoice I
      - Set the invoice date in the past and  add payment terms
      - Validate I
      - Create refund from I
      
      Bug:
      
      The invoice date is set as today but the due date was set in the past.
      
      opw:2033438
      
      closes odoo/odoo#34748
      
      Signed-off-by: default avatarSimon Goffin (sig) <sig@openerp.com>
      bb712ad7
    • Romain Derie's avatar
      [FIX] website, website_sale: correctly set company_id on address · 01c34a51
      Romain Derie authored
      
      During checkout, the user can create a new billing (only for public user as it
      will create a 'normal' `res.partner`), a new shipping, edit its billing (that
      will edit himself) or edit its shipping address.
      
      All those cases will go through the exact same methods, public user and logged
      in user included.
      
      This previously led to multiple issues and multiple fixes to correctly set
      `company_id` and `website_id` on the address (res.partner).
      
      See 44372471 that fixed the `website_id` part.
      
      See 3a0f05f3 that fixed the multi-company behavior, but needed 2ba71140 to not
      modify the company of an already created partner, but was still incomplete as
      after that fix a logged in user would still have the admin (sudo) company
      instead of the website one as supposed.
      
      This commit will fix that bug and add some tests for all mentionned issues.
      
      Fixes #28853
      
      Backport from odoo/odoo#34596
      
      closes odoo/odoo#34689
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      01c34a51
    • Romain Derie's avatar
      [FIX] website_sale: don't handle pl promo code if already applied · d24c1963
      Romain Derie authored
      
      When a pl promo code is applied, the code is shown in the promo code input.
      
      Before this commit, if the user clicked on "Apply" (so with the same code) it
      would remove the pl as it would go in the `if` condition that is supposed to
      handle empty code modo to reset pl.
      
      Coming from #34633
      
      closes odoo/odoo#34734
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      d24c1963
  28. Jul 09, 2019
    • Lucas Perais (lpe)'s avatar
      [FIX] l10n_be_intrastat, _2019: support rounding to 2 decimals · 06d149a3
      Lucas Perais (lpe) authored
      Before this commit, values were rounded to the unit, which was part of the former specs
      of the Intrastat report
      
      After this commit, we make the intrastat 2019 comply with the new spec, which is to round
      value, price and weight to two decimals
      
      See the spec here: https://www.nbb.be/doc/dq/f_pdf_ex/nieuwsbriefintrastat_n28_2018_fr.pdf
      
      
      
      OPW 2031682
      
      closes odoo/odoo#34700
      
      Signed-off-by: default avatarLucas Perais (lpe) <lpe@odoo.com>
      06d149a3
    • Richard Mathot's avatar
      [FIX] models: avoid Unicode error when translating that error message · 0ec0a4a3
      Richard Mathot authored
      
      The patch fa492d87 has been backported
      from Odoo 12.0, that runs on Python 3.
      
      The string '\n\n({} {}, {} {})' to be formatted is a byte-string in
      Python 2, while the return value of _() is always a unicode-string.
      
      As format() is (too?) nice, it attempts to convert the unicode-strings
      into ascii in order to inject them in the format pattern.
      With some languages that are written in ascii, this works -- by chance.
      When you use non-ascii languages like Japanese, it fails.
      
      We then fix that issue by using unicode-strings in the formatting
      pattern.
      
      #OneCharacterPatch B-)
      
      opw-2032016
      
      -----------------------------
      
      For full technical understanding:
      
      Python 2.7.16 (default, Mar 11 2019, 18:59:25)
      [GCC 8.2.1 20181127] on linux2
      Type "help", "copyright", "credits" or "license" for more information.
      >>> '{}'.format('test')
      'test'
      >>> '{}'.format(u'test')
      'test'
      >>> '{}'.format(u'エ')
      Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      UnicodeEncodeError: 'ascii' codec can't encode character u'\u30a8' in position 0: ordinal not in range(128)
      >>> u'{}'.format(u'エ')
      u'\u30a8'
      
      closes odoo/odoo#34698
      
      Signed-off-by: default avatarRichard Mathot (rim) <rim@openerp.com>
      0ec0a4a3
  29. Jul 08, 2019
Loading