Skip to content
Snippets Groups Projects
  1. Nov 27, 2022
  2. Nov 25, 2022
  3. Nov 24, 2022
    • Aurélien Warnon's avatar
      [FIX] base: allow user to modify its own preferences · 490d4804
      Aurélien Warnon authored
      
      The res.users model functions a bit uniquely since it should allow a user to
      modify their own parameters but turns off model edition priviledges by default.
      See "SELF_WRITEABLE_FIELDS".
      
      This implies that ir_ui_view#_postprocess_access_rights method will by default
      turn off record edition, by automatically adding a 'edit="false"' attribute on
      the form node when the frontend calls 'get_views'.
      
      This will in turn prevent the user from modifying its preferences as it will
      set the form view in readonly mode.
      (It was apparently ignored pre-OWL, hence why we only have this issue now).
      
      To fix the issue, we force the edition by manually setting 'edit="1"' on our
      "view_users_form_simple_modif" form.
      Allowing the end-user to modify their own settings again.
      
      A tour was added to ensure this behavior.
      Note that tour steps need to be adapted in the 'hr' module, as this module
      changes the flow of modifying user preferences.
      
      Task-3067001
      
      closes odoo/odoo#106125
      
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      490d4804
    • Odoo Translation Bot's avatar
  4. Nov 23, 2022
  5. Nov 22, 2022
  6. Nov 20, 2022
  7. Nov 14, 2022
    • FrancoisGe's avatar
      [FIX] *: override save checks that the save is valid · 46b93da5
      FrancoisGe authored
      
      The goal of this commit is to avoid the execution of code depending
      on the validity of the save of a Record.
      
      Before this commit, several override save functions in Record execute
      code after the record's save without checking if the record's save has
      taken place.
      
      Override before:
      export class NewRecord extends Record {
          async save() {
              const isSaved = await super.save(...arguments);
              // doAction
              return isSaved;
          }
      }
      
      Override after:
      export class NewRecord extends Record {
          async save() {
              const isSaved = await super.save(...arguments);
              if (isSaved) {
                  // doAction
              }
              return isSaved;
          }
      }
      
      How to reproduce the problem:
          Go to a form view with a Record having its save override function.
          Edit a record in such a way to have an invalid field
          Click on the save button
      
      Before this commit:
      The doAction is executed
      
      After this commit:
      The doAction is not executed
      
      Real use case
      - Go to the form view of a lead in CRM
      - Change stage
      - Clear the name field
      - Click on save button
      
      Before this commit:
      A call to get_rainbowman_message is made
      
      After this commit:
      No call to get_rainbowman_message is made.
      
      closes odoo/odoo#105468
      
      Related: odoo/enterprise#33817
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      46b93da5
  8. Nov 13, 2022
  9. Nov 06, 2022
  10. Oct 30, 2022
  11. Oct 24, 2022
  12. Oct 23, 2022
  13. Oct 21, 2022
  14. Oct 20, 2022
  15. Oct 17, 2022
  16. Oct 16, 2022
  17. Oct 10, 2022
  18. Oct 09, 2022
  19. Oct 07, 2022
    • Audric Onockx (auon)'s avatar
      [FIX] hr,hr_contract,resource: allocate hours before resource creation · 6a61d1c4
      Audric Onockx (auon) authored
      
      Steps :
      - On a new DB (no demo data). Say created at 15:00. - Go to planning.
      - Add a shift for today.
      - Set the dates from 08:00 to 17:00.
      
      Issue :
      The 'Allocated Time' = 02:00.
      
      Cause :
      We used to count from the resource creation min to the departure max. So, in this case, not from 08:00, but from 15:00.
      While this might seem logical, it confuses users in onboarding.
      
      Fix :
      Calculate the whole time, regardless of the resource lifespan.
      
      Notes :
      - Similar issues solved with this commit :
      > Once the shift validated, the avatar progress bar uses
      the same allocated time.
      > Same in Project Task gantt view.
      - When contract is installed, if the resource does not have a contract, the Allocated Time = 0. Now, it is calculated from the resource calendar.
      
      task-2983993
      
      closes odoo/odoo#102392
      
      Related: odoo/enterprise#32378
      Signed-off-by: default avatarLaurent Stukkens (ltu) <ltu@odoo.com>
      6a61d1c4
    • Rob Coekaerts's avatar
      [IMP] hr_homeworking: remove module · b3ad5886
      Rob Coekaerts authored
      
      The current homeworking module doesn't answer the standard of quality.
      For now It will be removed from the settings and app store so it is not visible
      to any users. It will return after it has been reviewed and  improved.
      
      task-2995332
      
      closes odoo/odoo#101093
      
      Related: odoo/enterprise#31762
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      b3ad5886
  20. Oct 06, 2022
  21. Oct 04, 2022
    • Martin Trigaux's avatar
      [I18N] *: export 16.0 source terms · 011d7aac
      Martin Trigaux authored
      
      closes odoo/odoo#102045
      
      Related: odoo/enterprise#32243
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      011d7aac
    • FrancoisGe's avatar
      [FIX] web: click on m2o_avatar in editable/multiEdit list · ad597d41
      FrancoisGe authored
      
      The goal of this commit is to fix the behaviour of clicking on a field
      with the "many2one_avatar" widget in a list view.
      
      Expected behaviour when clicking on a field with the "many2one_avatar" widget:
      - Editable list view: switch row to edit
      - Multi_edit list view with selected record: switch row to edit
      - Other case: open the many2one_avatar record in a form view
      
      Before this commit, clicking on a field with the "many2one_avatar" widget always
      opens the record in a form view.
      
      After this commit, the expected behaviour when clicking on a field with
      the "many2one_avatar" widget is respected.
      
      closes odoo/odoo#101737
      
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      ad597d41
  22. Oct 02, 2022
  23. Oct 01, 2022
    • Louis Wicket (wil)'s avatar
      [IMP] mail, *: refactor patch API to look like model definitions · 7d23491b
      Louis Wicket (wil) authored
      
      Model patches are now defined using the `registerPatch` function. This
      function takes an object as argument which keys match those of a model
      definition.
      
      Benefits:
      + More consistent shape between model definitions and patch definitions
      + No need to import one function to each type of patch
      + No need to repeat the model name for each type of patch
      + No need to import the original definition
      
      Task-2998282.
      
      * = calendar, crm, hr, im_livechat, note, rating, sms, snailmail,
          website_livechat, website_slides
      
      closes odoo/odoo#101282
      
      Related: odoo/enterprise#31866
      Signed-off-by: default avatarSébastien Theys (seb) <seb@odoo.com>
      7d23491b
  24. Sep 29, 2022
  25. Sep 26, 2022
    • Kevin Baptiste's avatar
      [FIX] hr: add missing fields on tree view · 8893c575
      Kevin Baptiste authored
      
      The domain of `work_location_id` requires the company_id and address_id
      which were missing from the tree view, showing a traceback when trying
      to change that field.
      
      closes odoo/odoo#101182
      
      X-original-commit: 8376adc1
      Signed-off-by: default avatarKevin Baptiste <kba@odoo.com>
      8893c575
    • Michael (mcm)'s avatar
      [IMP] web: remove readonly mode of form view · 77824ad4
      Michael (mcm) authored
      
      This commit does multiple things:
      - The readonly mode of form view is removed but not for the fields.
        it means that the fields in the view are always in edit mode except
        if we force them to be readonly.
      - The control panel is revamped to take less vertical space and shows now
        the record editing (dirtiness)/validity status after editing the record.
      - The record is saved only when leaving the view or by clicking the save
        button when hovering the record status in the control panel.
      - The record can still be discarded by clicking the discard button when
        hovering the status text in control panel.
      
      task id: 2822553
      
      Part-of: odoo/odoo#100570
      Co-authored-by: default avatarluvi <luvi@odoo.com>
      77824ad4
  26. Sep 25, 2022
  27. Sep 24, 2022
  28. Sep 23, 2022
Loading