Skip to content
Snippets Groups Projects
  1. Nov 12, 2019
  2. Oct 03, 2019
  3. Nov 12, 2019
  4. Nov 08, 2019
  5. Nov 06, 2019
  6. Nov 08, 2019
  7. Nov 10, 2019
  8. Nov 12, 2019
    • Andrea Grazioso (agr-odoo)'s avatar
      [FIX] google_calendar: exclusions not propagating (from OE) · 0f17a0ea
      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#39662
      
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      0f17a0ea
  9. Nov 08, 2019
  10. Nov 07, 2019
    • qsm-odoo's avatar
      [FIX] website: restore parallax previews in edit mode · 68b0f9cb
      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#39995
      
      X-original-commit: 4b633949cd4fd1cae807b95d233879ac4adc01ce
      Signed-off-by: default avatarQuentin Smetz (qsm) <qsm@odoo.com>
      68b0f9cb
  11. Nov 08, 2019
  12. Nov 06, 2019
  13. Nov 08, 2019
  14. Nov 07, 2019
    • Arnold Moyaux's avatar
      [FIX] purchase_requistion: call for tender zero lines · d8355a00
      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#39980
      
      Task: 2120211
      X-original-commit: 7d69f014
      Signed-off-by: default avatarArnold Moyaux <amoyaux@users.noreply.github.com>
      d8355a00
  15. Nov 08, 2019
  16. Nov 07, 2019
    • fw-bot's avatar
      [FIX] web: fix crash on editable list view when moving over a RO field · 6fae598d
      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#39976
      
      X-original-commit: 93c7ae9ba5309810c41c58fc8f2fafb3c3dac76e
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      6fae598d
    • Swapnesh Shah's avatar
      [FIX] website_sale: module sale_coupon is in community · aca5feb6
      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#39996
      
      X-original-commit: 959380eb
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      aca5feb6
    • Damien Bouvy's avatar
      [FIX] payment_paypal: include Build Notation reference · 69e54646
      Damien Bouvy authored
      
      closes odoo/odoo#39993
      
      X-original-commit: 75b1d412
      Signed-off-by: default avatarDamien Bouvy (dbo) <dbo@odoo.com>
      69e54646
    • laa's avatar
      [IMP] mail, mass_mailing: add dynamic placeholder mixin and use it in mailing and templates · 72aa0498
      laa authored
      PURPOSE
      
      Upgrade the "mass_mailing" and "mass_mailing_sms" modules with a dynamic
      placeholder generator as it already exists in "mail module" as depicted in
      https://www.screencast.com/t/cnFA0gIY
      
      .
      
      SPECIFICATIONS
      
      As duplicated code already exists for that and that a third version of this
      code has to be added, instead create a mixin for this dynamic placeholder
      generator to avoid code duplication.
      
      Thereby
      
        * a mail.render mixin for the dynamic placeholder generator must be
          created in mail;
        * dynamic placeholder generator code present in mail.template.py must be
          moved to that mixin and replaced by a simple inherit;
        * use the mixin in
      
          * mail templates: mail.template.py (mail module);
          * mass mailings: mailing.py (mass_mailing module);
          * sms templates: sms.template (mass_mailing_sms module);
      
      In a near future, some code will be added in this mixin, notably the template
      rendering that could be moved outside of mail.template core model and moved
      in that rendering mixin.
      
      LINKS
      
      Task ID 2070612
      PR #36722
      
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      72aa0498
    • Swapnesh Shah's avatar
      [FIX] event: Set default value for event_count · dc70fb35
      Swapnesh Shah authored
      Fixes https://github.com/odoo/odoo/pull/39583
      
      
      This commit adds a default value for  event_count
      Assigning default value for non-stored compute fields is required in 13.0
      
      closes odoo/odoo#39974
      
      X-original-commit: 9ca72b98
      Signed-off-by: default avatarVictor Feyens (vfe) <vfe@odoo.com>
      dc70fb35
    • alt-odoo's avatar
      [FIX] website: display archived website visitors · 4b0fdffe
      alt-odoo authored
      
      When computing time statistics, we need to look for
      archived website visitors also to avoid a KeyError
      if we use the default 'Archived' filter.
      
      closes odoo/odoo#39970
      
      X-original-commit: fe4d9bd2
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      4b0fdffe
    • Andrea Grazioso (agr-odoo)'s avatar
      [FIX] sale: wrap long line in sale portal · 962d6c23
      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#39968
      
      X-original-commit: 28afbaf5
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      962d6c23
    • jvm-odoo's avatar
      [FIX] crm: fix lead/opportunity meeting scheduling · e5adee2e
      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#39964
      
      X-original-commit: 59d154dc
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      e5adee2e
    • qsm-odoo's avatar
      [FIX] web: prevent destroyed widget from calling start (2) · 60d1e26f
      qsm-odoo authored
      This completes a commit that was made for the version saas-11.3 (12.0):
      https://github.com/odoo/odoo/commit/1440c8be0337c89e3d67d6d93e614c269c8689f1
      
      
      
      Indeed, the logic was implemented for the appendTo, prependTo, etc
      methods but not for the attachTo...
      This could solve unknown problems in stable versions as well but was
      judged too risky to merge there. Indeed, if a real problem occurs in a
      stable version because of this, the condition can be added to the
      related widget individually.
      
      The problem was found in master: during website edition, the public
      widgets can be restarted if an element is edited... but sometimes the
      public widgets may be restarted in the same JS stack execution. The
      willStart method being async, the destroy method was called before
      the start method. This does not lead not any known problem with our
      current widgets but will create one for a new snippet being implemented.
      
      closes odoo/odoo#39949
      
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      60d1e26f
    • fw-bot's avatar
      [FIX] hr: make hr.job visible without recruitment · 7a18176c
      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#39948
      
      Taskid: 2088277
      X-original-commit: e4de2b2e
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      7a18176c
Loading