Skip to content
Snippets Groups Projects
  1. Nov 06, 2019
  2. Oct 30, 2019
  3. Nov 06, 2019
  4. Nov 05, 2019
  5. Nov 04, 2019
    • jvm-odoo's avatar
      [FIX] account: fix mass mail wizard · 2496125f
      jvm-odoo authored
      - In the sales or accounting module, create some invoices.
      - Select them then click on `action > send & print`
      - The wizard opens but not in the mass mail mode.
      
      It creates some inconsistency and if you click on send,
      the invoices are sent to the wrong customer.
      
      Sometimes, the invoices are not sent at all.
      
      I think the problem comes from the `_compute_composition_mode` method
      who set the value of `composition_mode` on the wizard instead of
      on the composer.
      
      OPW-2085837
      2496125f
  6. Nov 06, 2019
  7. Nov 04, 2019
  8. Nov 06, 2019
  9. Nov 05, 2019
  10. Oct 30, 2019
    • Christophe Monniez's avatar
      [FIX] packaging: compute winpython path with package.py args · ac90d858
      Christophe Monniez authored
      
      When building the MS Windows package, the PYTHON_VERSION variable is not
      used and the WinPython path is hard coded in the Makefile and NSI file.
      This prevent the usage of a newer version of Python.
      
      With this commit, the PYTHON_VERSION is used to compute the WinPython
      Python directory. That way, this directory can be derived from
      package.py command line argument --vm-winxp-python-version.
      
      Also the less windows binaries are not packaged anymore.
      
      closes odoo/odoo#39816
      
      Signed-off-by: default avatarChristophe Monniez (moc) <moc@odoo.com>
      ac90d858
  11. Nov 05, 2019
    • jvm-odoo's avatar
      [FIX] project: fix multi level subtask · 41173789
      jvm-odoo authored
      
      - Create a project
      - Create 3 tasks in the project (top, middle, bottom)
      - Set top as the parent of middle
      - Set middle as the parent of bottom
      
      We don't want to allow multi level subtasks. The behavior is not the
      same if you set middle as the parent of bottom first. The "parent task"
      field will not be displayed.
      
      This commit remove the tasks who have a parent from the m2o field.
      
      OPW-2087921
      
      closes odoo/odoo#39805
      
      X-original-commit: c7966b64
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      41173789
    • wan's avatar
      [FIX] account: payment reference exact match without spaces · 9b5d1f6b
      wan authored
      
      The spaces should not be important in a structured reference.
      Also, we should not have to include the second batch as that batch
      (previously the first) was intended to match the payment reference.
      By including it, we may have too much false positives proposed in the
      widget and even worse: auto reconciled.
      
      closes odoo/odoo#39334
      
      Signed-off-by: default avatarQuentin De Paoli (qdp) <qdp@openerp.com>
      9b5d1f6b
  12. Oct 31, 2019
    • wan's avatar
      [FIX] account: match on sanitized bank number · 733ca62a
      wan authored
      FIX 2092459
      The reconciliation tries to find partner based on the bank number, but
      that bank number may not be encoded the same way depending where the
      statement lines come from.
      A solution is to sanitize the bank number at query time.
      733ca62a
  13. Nov 05, 2019
    • Adrian Torres's avatar
      [FIX] base: avoid triggering recomputation when deleted selection · 0ccf2ab8
      Adrian Torres authored
      
      In 6b048a8b most issue with trigger causing error when uninstalling a
      module were solved.
      
      But there was a particular case if the current uninstallation of modules
      there was an update of `ir.model.fields.selection` to be removed. The
      unlink of `ir.model.fields.selection` would cause a `setup_models` call
      that would add all removed triggers back and possibly down the line
      cause an trigger recomputation error.
      
      With this changeset, we do as is already done for ir.model.fields and do
      not re-initialize the registry during module uninstallation.
      
      opw-2098915
      closes #39796
      
      Signed-off-by: default avatarAdrian Torres (adt) <adt@odoo.com>
      0ccf2ab8
  14. Nov 04, 2019
    • jvm-odoo's avatar
      [FIX] event: fix email sent on duplicates · 9d9508bb
      jvm-odoo authored
      
      - Create an event
      - Add a mail reminder for it
      - Run the mail scheduler manually
      - Duplicate the event
      
      The mail reminder is sent on the duplicate too.
      This commit remove the field `mail_sent` from duplicating.
      
      OPW-2117343
      
      closes odoo/odoo#39770
      
      X-original-commit: 7fede2c0
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      9d9508bb
    • Damien Bouvy's avatar
      [FIX] sale(_timesheet): faulty computation · cf54606e
      Damien Bouvy authored
      
      The 'delivered quantity' field sometime needs to trigger a search
      on related objects (e.g. analytic lines) to know how much has been
      delivered.
      
      For performance reasons, this search is done using a read_group where
      the results are grouped by SO line.
      
      Unfortunately, this computation is sometimes launched during
      recomputes/onchanges where the line in question has a NewId instead
      of a regular id.
      
      This means that the mapping will return something like
      {240: 50.0}
      indicating that (e.g.) there are 50 timesheet hours for the SO line
      with id 240; unfortunately by doing
      mapping.get(line.id, 0.0)
      the NewId (240) is used - therefore returning a delivered quantity
      of 0.0 for a line which has actual timesheets.
      
      This commit ensures that if the line has a NewId and an original
      underlying record, the id of the latter is used as the key to fetch
      the value from the dict that contains the read_group result.
      
      Note that the problem was quite tricky to reproduce as it depended
      on the order of operations launched by triggers - the order of
      operations was important since triggering the compute with the 'real'
      record put things in order before any other piece of code could have
      spotted the issue.
      
      closes odoo/odoo#39778
      
      Signed-off-by: default avatarDamien Bouvy (dbo) <dbo@odoo.com>
      cf54606e
    • Adrian Torres's avatar
      [FIX] stock: allow unlinking records in uninstall mode · cedafe00
      Adrian Torres authored
      
      Business cases should not prevent the unlink of module-related records
      during an uninstall.
      
      This commit allows the reinstallation of sale_stock with demo data and
      also allows the proper removal of tables and records if a db has any
      non-draft inventory adjustments.
      
      closes odoo/odoo#39764
      
      Signed-off-by: default avatarAdrian Torres (adt) <adt@odoo.com>
      cedafe00
    • qsm-odoo's avatar
      [FIX] web_editor: put the snippet editor UI at the correct DOM position · 86d12706
      qsm-odoo authored
      Commit https://github.com/odoo/odoo/commit/4f27e52cabb77b8b1a9637a11185ddf882adc9af
      
      
      had to instantiate the snippet editor UI differently but the hack broke
      the position of the oe_manipulator which is supposed to be at the top
      left of the editable zone.
      
      closes odoo/odoo#39751
      
      Signed-off-by: default avatarQuentin Smetz (qsm) <qsm@odoo.com>
      86d12706
    • qsm-odoo's avatar
      [FIX] web_editor: do not reposition overlay over an hidden element · b8d7c69d
      qsm-odoo authored
      Could be the cause of flickering during multiple recomputation of the
      overlay position.
      b8d7c69d
    • Julien Castiaux's avatar
      [IMP] doc: clarify dep installation for linux · f7d0022f
      Julien Castiaux authored
      
      Someone new to Linux can run into problems when some system dependencies
      are missing. There is a single sentence warning talking about those hard
      dependencies and it does not explain how to install them.
      
      Added two § containing the missing `apt` commands required to install
      the dependencies on a fresh debian minimal install.
      
      closes odoo/odoo#38948
      
      Signed-off-by: default avatarJulien Castiaux <Julien00859@users.noreply.github.com>
      f7d0022f
    • Paul Morelle's avatar
      [FIX] link_tracker: support any url · 616e1456
      Paul Morelle authored
      
      URLs with parameters were not correctly supported by the regular
      expression.
      For example, URLs with parameters were truncated before the '?'.
      
      This patch adds support for a wider range of URLs, and checks in a test
      that the parameters are correctly handled.
      
      closes odoo/odoo#39716
      
      Signed-off-by: default avatarRémi Rahir (rar) <rar@odoo.com>
      616e1456
    • jvm-odoo's avatar
      [FIX] base: fix merge partner wizard · 014f3bbc
      jvm-odoo authored
      
      In the contacts app, you can select 2 partners and merge them.
      
      Before this commit:
      
          - If a partner was added by a SQL query and not directly on Odoo,
            the create_date will be empty. This causes a crash because the
            merge wizard try to sort the partners by date
      
      After this commit:
      
          - If a partner do not have a create_date, it will be considered
            as 01/01/1970. The merge wizard will sort the partners by IDs too.
      
      OPW-2091925
      
      closes odoo/odoo#39518
      
      X-original-commit: deeb769c
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      014f3bbc
    • Nicolas Lempereur's avatar
      [FIX] sale: have sender in SO confirmation email · 6aebb523
      Nicolas Lempereur authored
      
      Before 13.0 .sudo() before sending a mail would send it as superuser user
      (which was the intention in this case), but since 13.0 for the same
      intention we need .with_user(SUPERUSER_ID).
      
      Without this change, the confirmation email on a sale order would have
      no sender ending up in failure.
      
      opw-2118612
      closes #39737
      
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      6aebb523
    • Nicolas Lempereur's avatar
      [FIX] website_sale: send extra step as public user · 7b1654a1
      Nicolas Lempereur authored
      
      The extra informations not on the sale.order models were sent before
      13.0 with the superuser user. In 13.0 with the change of `sudo` and
      `with_user` behavior, we were now in superuser mode but not with the
      superuser so the mail would error (no from address) and the sale order
      would error.
      
      With this changeset, we get back to the pre-13 behavior.
      
      opw-2116346
      closes #39730
      
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      7b1654a1
    • Aaron Bohy's avatar
      [FIX] web,sale_product_matrix: allow to open matrix · 49626acb
      Aaron Bohy authored
      
      Before this rev, it crashed when opening the (sale or purchase)
      product matrix (e.g. on runbot, go to quotations, create, add a
      line, select 'My Company tshirt').
      
      This was due to a recent override of _applyChanges (see 4bf98b47),
      which didn't return the value returned by super.
      
      OPW 2116083
      
      closes odoo/odoo#39717
      
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      49626acb
    • Xavier Morel's avatar
      [FIX] core: SIGXCPU in worker processes · 659fcfec
      Xavier Morel authored
      
      odoo/odoo#30688 (6ce2d6ef) added an
      indirection in prefork workers: Python-level signal handlers are
      delayed until native calls have ended (e.g. accept() or
      execute()). Running the actual work in a sub-thread allowed the main
      thread to handle signals in all cases.
      
      However there is apparently an issue with SIGXCPU on linux (possibly
      other cases as well): SIGXCPU is delivered to the child thread (if
      possible?) and Thread.join apparently stops it from redelivered to
      the main thread (Thread.join is signal-interruptible since 3.2 but
      possibly not Python-interruptible).
      
      Blocking SIGXCPU on the child thread causes the OS to deliver on the
      main thread and fixes the issue.
      
      Also split set_limits so it sets the signal handler in the parent
      thread but properly updates the soft limit in the child after each
      request, as the goal is to put a hard limit on the CPU time per
      request, not on the worker. 6ce2d6ef would set the limit once then
      never update it, likely cycling workers more than desired.
      
      While at it:
      
      * block other signals with a handler set, they seem to work
        regardless on linux but other OS may have a different way of
        dispatching process-directed signals
      * unset signals which are set by the prefork server but whose
        set behavior makes no sense in workers:
      
        - TERM and CHLD were already unset
        - HUP is used to restart the server, workers can just be killed
        - TTIN and TTOU configure the number of workers
      
      closes odoo/odoo#39723
      
      X-original-commit: 549bd199
      Signed-off-by: default avatarXavier Morel (xmo) <xmo@odoo.com>
      659fcfec
    • Joseph Caburnay's avatar
      [FIX] point_of_sale: uninvoiced orders' state not set to 'done' · bb490301
      Joseph Caburnay authored
      
      Prior to this commit: b234e97f,
      uninvoiced orders' state is set to 'done' when the session is validated.
      However, this was not taken into consideration in the said commit such
      that even if the session is already validated, the uninvoiced orders'
      state remains 'paid'.
      
      Setting the orders state to 'done' is the correct behavior and is
      implemented in this commit.
      
      closes odoo/odoo#39720
      
      Signed-off-by: default avatarpimodoo <pimodoo@users.noreply.github.com>
      bb490301
Loading