Skip to content
Snippets Groups Projects
  1. Nov 08, 2019
  2. Nov 07, 2019
    • Arnold Moyaux's avatar
      [FIX] purchase_requistion: call for tender zero lines · 02ba6139
      Arnold Moyaux authored
      
      Usecase to reproduce:
      - Create a purchase requistion with type Call For Tender
      - Update a line and set the price to zero.
      
      UserError 'You cannot confirm the blanket order without price.' raised.
      It happens because the write don't process the same check than create
      and don't check if the purchase_requistion is a blanket order or a call
      for tender. It also doens't check the current state of the
      purchase_requisition.
      
      closes odoo/odoo#39973
      
      Task: 2120211
      X-original-commit: 7d69f014
      Signed-off-by: default avatarArnold Moyaux <amoyaux@users.noreply.github.com>
      02ba6139
    • qsm-odoo's avatar
      [FIX] website: restore parallax previews in edit mode · 3c5a2724
      qsm-odoo authored
      
      When the user changed the parallax option, it was only updated on save.
      So, the user was not able to have a preview of what he chose.
      
      Note: this commit is made in saas-12.3 but does not fully solve the
      problem there... and unfortunately I don't know why. It fully solves
      the problem in 13.0 though and this is more important.
      
      closes odoo/odoo#39991
      
      X-original-commit: 4b633949cd4fd1cae807b95d233879ac4adc01ce
      Signed-off-by: default avatarQuentin Smetz (qsm) <qsm@odoo.com>
      3c5a2724
    • Nicolas Martinelli's avatar
      [FIX] website: access website in multi-company · debc516c
      Nicolas Martinelli authored
      
      - Create 2 companies A & B
      - Create a website A
      - Create a user U with access to company B only
      - Connect as U and go to the website
      
      An internal server error is raised.
      
      This is due to 7bfcb53d which verifies if the user isn't
      granted access to companies he is not supposed to access.
      
      This is exactly what was done before this commit: the website is in a
      company not allowed to the user.
      
      opw-2116539
      
      closes odoo/odoo#39921
      
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      debc516c
  3. Nov 06, 2019
  4. Oct 31, 2019
    • Andrea Grazioso (agr-odoo)'s avatar
      [FIX] google_calendar: exclusions not propagating (from OE) · c35d87dd
      Andrea Grazioso (agr-odoo) authored
      Activate Google Synchronization, create on OE a recurrent event,
      synchronize the calendar, then delete an event of the recursion on GC,
      sync again on OE.
      
      The event will be deleted from GC but not from OE after sync.
      
      This appens because of this "rewrite" rule
      https://github.com/odoo/odoo/blob/12.0/addons/calendar/models/calendar.py#L918
      
      
      that occur on event creation from OE, altering the event parameters when
      is marked "allday".
      
      When an "allday" event is deleted from GC the unlink is triggered in OE with the
      default time "00:00:00". During the creation of the exclusion '
      _inverse_dates' will be called altering start and stop datetime but not
      recurrent_id_date, so the new record will not match the event generating
      the recursion and the exclusion will not occur. The problem require
      particular carefulness because when a recurrent event is fetched from
      google the '_inverse_dates' is not called, so in that case the default
      time is fine.
      
      opw-2060526
      
      closes odoo/odoo#39653
      
      X-original-commit: a468464c
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      c35d87dd
  5. Nov 04, 2019
    • jvm-odoo's avatar
      [FIX] base: fix merge partner wizard · 1a498a50
      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#39758
      
      X-original-commit: df09f2f73ddf917304906e98725324319c309939
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      1a498a50
  6. Nov 07, 2019
    • fw-bot's avatar
      [FIX] web: fix crash on editable list view when moving over a RO field · 2b36a605
      fw-bot authored
      
      In editable list view, moving to next cell using TAB key crash when the
      following field is read-only (i.e non-focusable) and an onchange() event
      is triggered.
      
      Consider an editable tree view like this:
      
      <form>
         <field name="o2m" onchange="1">
             <tree>
                <field name="description"/>
                <field name="date" readonly="1"/>
                <field name="type"/>
             </tree>
         </field>
      </form>
      
      1. Adding a new line will give focus to `description` field widget
         (currentFieldIndex is 0)
      
      2. issuing a TAB keypress, will call _onNavigationMove which calls
         _selectCell() with fieldIndex of 1
      
      3. The _selectCell() method set widget currentFieldIndex to the new value
         (currentFieldIndex is 1) add call _activateFieldWidget() to activate
         on the corresponding widget.
      
      4. _activateFieldWidget() will fail to activate the `date` field as it's
         readonly, then try for next ones and succeed to activate the `type` field
         cell
      
      5. When focus is given a `type`, the `description` field is blurred which
         trigger an onchange() and the controller apply those changes to the
         editable list rendererd using the confirmUpdate() method.
      
         The confirmUpdate() will try to get the current selection, but that
         field is actually set to the `date` field (currentFieldIndex = 1),
         which is readonly and so has no focusedElement - triggering the crash.
      
      This commit ensure we don't try to call getSelectionRange() it current widget
      has no focusable element.
      
      OPW-2075229
      
      closes odoo/odoo#39972
      
      X-original-commit: 93c7ae9ba5309810c41c58fc8f2fafb3c3dac76e
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      2b36a605
    • Swapnesh Shah's avatar
      [FIX] website_sale: module sale_coupon is in community · 959380eb
      Swapnesh Shah authored
      Follow up on https://github.com/odoo/odoo/commit/ac5469646cdea7c0990fbd5092eae26e7e0768ae#diff-04174b6f17e548b9a79222ae09c573db
      
      
      Before this Commit, upgrade_boolean was applied on sale_coupon module while this has been moved to the community version from v13, so upgrade_boolean is not needed now
      
      closes odoo/odoo#39985
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      959380eb
    • Damien Bouvy's avatar
      [FIX] payment_paypal: include Build Notation reference · 0d60a50b
      Damien Bouvy authored
      
      closes odoo/odoo#39987
      
      X-original-commit: 75b1d412
      Signed-off-by: default avatarDamien Bouvy (dbo) <dbo@odoo.com>
      0d60a50b
    • Thibault Delavallée's avatar
      [FIX] mail: use queue to send channel guidelines · 29688cdf
      Thibault Delavallée authored
      
      Commit 775e8a9f forced channel guidelines to be sent directly. It seems
      safer to use the cron queue as we do not see any evidence of daily use of
      channel guidelines requiring immediate sending.
      
      Task ID 2121319
      PR #39978
      
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      29688cdf
    • Thibault Delavallée's avatar
      [FIX] mail: correctly format rejection email moderation content · bfcf7b04
      Thibault Delavallée authored
      When an incoming email on a channel is rejected, an email is sent to the
      original author to inform him of the rejection. This email contains the
      original email content added in a generic rejection email.
      
      This original content was however considered as plaintext and escaped. Result
      was quite hard to read. As content is sanitized we can safely append it to
      the rejection email as valid html.
      
      Task ID 2121319
      PR #39978
      bfcf7b04
    • Andrea Grazioso (agr-odoo)'s avatar
      [FIX] sale: wrap long line in sale portal · 6e6d6833
      Andrea Grazioso (agr-odoo) authored
      
      From Sale create a new (or edit) SO. Add a note to the order with a log
      line without dash or whitespace (i.e. a url). Click on "Preview".
      
      The sale portal will try to display the long line which will overflow
      the standard size of the column creating an ugly overflow with a very
      long horizontal scrollbar.
      
      Adding a "break-all" rule to fix the sale portal case.
      
      opw-2088589
      
      closes odoo/odoo#39966
      
      X-original-commit: 28afbaf5
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      6e6d6833
  7. Oct 30, 2019
  8. Nov 06, 2019
  9. Nov 07, 2019
    • jvm-odoo's avatar
      [FIX] crm: fix lead/opportunity meeting scheduling · a2c7e6e3
      jvm-odoo authored
      
      Reproduce the issue:
       - In the CRM app, create a lead/opportunity.
       - Schedule a meeting for this opportunity via
         the chatter and click on create.
       - Go back, the "Meeting" stat button is now at 1
       - Schedule a meeting for this opportunity via
         the chatter and click on edit then create.
       - Go back, the "Meeting" stat button is still at 1
      
      Cause:
      When we click directly on create, the opportunity ID is in the defaults
      option but when we click on edit, there is no opportunity ID.
      
      So, this commit use the context to retrieve the concerned opportunity
      and set it if it is not already set.
      
      I splitted the solution into a private method for a better readability.
      
      OPW-2092920
      
      closes odoo/odoo#39952
      
      X-original-commit: 59d154dc
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      a2c7e6e3
    • fw-bot's avatar
      [FIX] hr: make hr.job visible without recruitment · e4de2b2e
      fw-bot authored
      
      Without hr_recruitment it was not possible to import/export the hr.job
      as they were not visible.
      
      closes #22069
      
      closes odoo/odoo#39914
      
      Taskid: 2088277
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      e4de2b2e
  10. Nov 06, 2019
  11. Oct 30, 2019
  12. Nov 06, 2019
  13. Nov 05, 2019
  14. 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
  15. Nov 06, 2019
  16. Nov 04, 2019
  17. Nov 06, 2019
Loading