Skip to content
Snippets Groups Projects
  1. Oct 16, 2019
  2. Oct 11, 2019
  3. Oct 16, 2019
    • fw-bot's avatar
      [FIX] base: Allow default email_from by database · c06b4f52
      fw-bot authored
      
      It is possible to get to a situation where Odoo would try to send an email without a `From:` header address.
      
      In such case, you're unlucky if you don't have access to the underlying deployment, or if you use multiple databases in a single Odoo instance and each of them uses a different mail configuration.
      
      To make this configuration easier to use and cover those use cases, here I add support for a new ICP: `mail.default.from`. It will be used when present, so it shouldn't affect existing deployments. When present, it will allow a admin to configure the default sending address just with Odoo itself.
      
      closes odoo/odoo#38865
      
      X-original-commit: 5010ce63
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      c06b4f52
  4. Oct 15, 2019
  5. Oct 14, 2019
  6. Oct 10, 2019
  7. Oct 16, 2019
  8. Oct 15, 2019
    • Arturo Flores's avatar
      [IMP] l10n_pe: improve how we display the address for Peru · 24a3571e
      Arturo Flores authored
      
      Once we add an address in Peru we need it to be displayed in the next
      way for the reports:
      
      Name of the partner
      Street name, number
      Apartment(optional)
      District
      City
      
      The level State and Country are added to complement the street address.
      
      closes odoo/odoo#38764
      
      Signed-off-by: default avatarJosse Colpaert <jco@openerp.com>
      24a3571e
    • Arturo Flores's avatar
      [FIX] l10n_pe, base_vat: Finish prepration for l10n_pe_edi · 88681f8f
      Arturo Flores authored
      - base_vat: Correct management of the check of peruvian VAT without prefix.
      - l10n_pe: Correct income account the last one is not correct.
      - l10n_pe: Forced Round globally for peruvian companies once l10n_pe is
      installed, and with the onchange.
      - l10n_pe: For peruvian companies it does not make sense a sequence per
      year and the year in the prefix is incorrect, we must force XXX- as
      a sequence prefix.
      88681f8f
  9. Oct 16, 2019
  10. Oct 15, 2019
  11. Oct 10, 2019
  12. Oct 15, 2019
    • Olivier Dony's avatar
      [FIX] bus,im_support: adapt im_support to bus changes · d886aff3
      Olivier Dony authored
      
      The im_support module was broken in 12.0 after bus refactorings between
      11.0 and 12.0.
      
      closes odoo/odoo#38831
      
      X-original-commit: db37e0ce
      Signed-off-by: default avatarOlivier Dony (odo) <odo@openerp.com>
      Co-authored-by: @alexkuhn
      d886aff3
    • Lucas Perais (lpe)'s avatar
      [FIX] account: reconciliation widget fetch correct reconciliation models · c285d578
      Lucas Perais (lpe) authored
      
      Have a reconciliation model that applies to some particular journals
      And that will match some of those journals' lines
      The field journal should be filled too
      (this field is only the default journal that a proposition will be filled with)
      
      Open the reconciliation widget on a given journal, within the list of
      possible journal (from the account dashboard)
      
      Before this commit there was a crashed. This was caused by the fact that
      one of the lines that should be displayed had a reconcile model that was not fetched beforehand
      
      After this commit, there is no crash as all relevant reconcile
      models are fetched
      
      Note that, on reconcile models, the field journal_id is just there to prefill
      the propositions it will create
      
      corrects commit e5c80714
      
      OPW 2084942
      
      closes odoo/odoo#38817
      
      X-original-commit: 2f4344cce6672e5dbe319047c5c7db293a05ba54
      Signed-off-by: default avatarLucas Perais (lpe) <lpe@odoo.com>
      c285d578
    • Martin Trigaux's avatar
      [FIX] event: print registrations without name · 4e341a2f
      Martin Trigaux authored
      
      Before this commit, trying to print a registration without a name
      specified (not required), was failing
      
      Fixes odoo/odoo#38564
      
      Replace and closes odoo/odoo#38582
      Courtesy of Swapnesh Shah
      
      closes odoo/odoo#38811
      
      X-original-commit: a21a81e9
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      4e341a2f
  13. Oct 10, 2019
    • Katherine Zaoral's avatar
      [FIX] l10n_ar: Properly compute fiscal position for Argentinian · 74f17204
      Katherine Zaoral authored
      companies.
      
      We revert the change we apply in order to let the user to define their
      own fiscal positions, now the fiscal position will be set depending on
      the afip responsability.
      
      With this change we fix the error that the fiscal position is properly
      setted for the customers that are of type "Responsable Inscription" and
      "Consumidor Final".
      
      Before this change the "Compras / Ventas en el Exterior" fiscal position
      was wrongly seted, now the fiscal position is leave empty so the related
      invoice taxes are properly matched
      
      closes odoo/odoo#38431
      
      Signed-off-by: default avatarJosse Colpaert <jco@openerp.com>
      74f17204
  14. Oct 11, 2019
  15. Oct 15, 2019
  16. Oct 14, 2019
    • Adrian Torres's avatar
      [FIX] base: don't crash during CRUD if record does not exist · f3b05032
      Adrian Torres authored
      
      - Let a model M define a Many2oneReference field F1.
      - Let a model N define a One2many field F2 whose inverse is M->F1
      - Define a computed field N->F3 that depends on N->F2
      
      If, for whatever reason, a recordset of M contains records that have
      been unlinked already and we try to unlink them again, the system will
      crash with a MissingException error.
      
      This happened because, while most _modified_trigger cases cover the case
      of a MissingException (i.e. record not in cache), the case for a
      Many2oneReference didn't.
      
      This is fixed by simply ignoring these "stale" records in the
      _modified_triggers section for Many2oneReference fields.
      
      closes odoo/odoo#38697
      
      Signed-off-by: default avatarRaphael Collet (rco) <rco@openerp.com>
      Co-authored-by: default avatarmreficent <miquel.raich@eficent.com>
      f3b05032
  17. Oct 15, 2019
  18. Oct 08, 2019
  19. Oct 15, 2019
  20. Oct 14, 2019
    • fw-bot's avatar
      [FIX] base: impossible to change contact name format · f339f8bf
      fw-bot authored
      
      - Create a sales order for a company with a contact name.
      - Click the Preview button.
      - The company and contact names appear on the same line, only separated by a
      comma.
      
      Before this commit:
      
      it's not possible to easily override this behavior.
      
      After this commit:
      
      it's possible to override `Partner._get_contact_name` to change the format of
      contact name.
      
      Beware that this method is used in `_get_name` which is called from various
      places. A check on the context may be necessary.
      
      closes odoo/odoo#38701
      
      Opw: 2077294
      X-original-commit: 0b8f3f93a2cb05cc9c940964fe80acd23b86b8a0
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      f339f8bf
    • Alexandre Kühn's avatar
      [FIX] mail: messaging ready after 1st chatter rendering · 5f25bc2d
      Alexandre Kühn authored
      Revision on https://github.com/odoo/odoo/commit/9a66619db33fca5f0cb81d9f6bfeb0fb0290cf68
      
      
      
      Commit above improves the web client startup by not having to wait
      for discuss widgets to fully load beforehand.
      
      However, it introduced an issue with chatter when the 1st rendering
      happens before messaging becomes ready: it displays
      "Creating a record..." instead of the whole history of messages.
      This happens because when messaging is ready, it updates data from
      the chatter but it does not trigger a re-render.
      
      This commit fixes the issue by triggering a re-render on messaging
      ready. When messaging is not ready, thread field now displays
      "Loading..." instead of the message "Creating a record...".
      
      Task-Id 2078193
      
      closes odoo/odoo#38749
      
      X-original-commit: 93bdd7c91095025f4d6e7a058e0ab1c4e1a0ad60
      Signed-off-by: default avatarAlexandre Kühn (aku) <aku@odoo.com>
      5f25bc2d
    • Christophe Simonis's avatar
      [FIX] hr_holidays: force empty value in xml declaration · df680ad1
      Christophe Simonis authored
      
      Ease module upgrade.
      
      closes odoo/odoo#38741
      
      Signed-off-by: default avatarChristophe Simonis <chs@odoo.com>
      df680ad1
    • Christophe Monniez's avatar
      [FIX] packaging: include python3-xlrd in debian package · de241dcd
      Christophe Monniez authored
      As the python3-xlrd package is available in Debian stretch and Ubuntu
      bionic, there is no reason to not include it in Odoo debian package.
      
      However, it cannot be used in Odoo 11.0 package as it does not exists in
      Ubuntu Xenial.
      
      ubuntu package:
      https://packages.ubuntu.com/bionic/python3-xlrd
      
      debian package:
      https://packages.debian.org/stretch/python3-xlrd
      
      
      
      closes odoo/docker#276
      
      closes odoo/odoo#38742
      
      X-original-commit: acf413df
      Signed-off-by: default avatarChristophe Monniez (moc) <moc@odoo.com>
      de241dcd
    • Sébastien Theys's avatar
      [FIX] website, website_theme_install: fix theme selection in settings · 2298ef19
      Sébastien Theys authored
      
      Follow up of commit a3845ae3
      
      Issue
      =====
      
      Since the above commit there is a confirmation dialog when clicking on a button,
      for which the only options are to Discard or Cancel.
      
      The problem is that when discarding it will revert the selected website back to
      the default value. Therefore before the current commit it is impossible to
      install a theme on a website other than the first.
      
      Solution
      ========
      
      The solution is to avoid showing this dialog when clicking on buttons for which
      the result depends on the currently selected website. This leads to the same
      behavior as what existed before the mentioned commit: the settings are
      implicitly discarded because they are not saved, but at the time of the click
      the transient model still holds the non-discarded value that the user selected.
      
      This restores the "select a theme" feature, but also restores the unfortunate
      side effect that the user might unknowingly loose all of his pending changes
      when clicking on the button, but only for those two specific buttons.
      
      Other considerations
      ====================
      
      Saving instead of Discarding was considered but it is impossible to do because
      saving might do a lot of changes that might even lead to the installation of
      modules, so the settings page has to be reloaded to apply them, and then the
      website field will be reset to its default value again.
      
      Instead of changing website specific settings from the main settings, it was
      considered to update them through a form view, but it is apparently too
      complicated for on-boarding.
      
      The last consideration was that the settings view should actually mark the
      corresponding fields as unchanged when changing the website, but it is too
      complex to implement for a case that is not supported in the first place,
      especially for a fix in a stable version.
      
      task-2083198
      
      closes odoo/odoo#38716
      
      Signed-off-by: default avatarSébastien Theys (seb) <seb@odoo.com>
      2298ef19
Loading