Skip to content
Snippets Groups Projects
  1. Feb 17, 2016
    • Olivier Dony's avatar
      [FIX] analytic: name_search with negative operators · 1e729c7c
      Olivier Dony authored
      The algorithm for matching analytic accounts based
      on search term is only meant to be used for
      simple, positive operators.
      In other cases the results will not be what the user
      expects. Falling back to the default name_search
      behavior will be more useful.
      1e729c7c
    • Goffin Simon's avatar
      [FIX] account : tax details in invoice report · 598856e1
      Goffin Simon authored
      When a tax with an amount of 0 percent was linked to an invoice line,
      this tax didn't appear in the tax details in the bottom of the invoice
      report.
      
      opw669162
      598856e1
  2. Feb 16, 2016
  3. Feb 15, 2016
  4. Feb 14, 2016
  5. Feb 12, 2016
    • Goffin Simon's avatar
      [FIX] sale: Ordered Qty=0 in a SO line · 1f081bed
      Goffin Simon authored
      A SO line with an ordered qty less or equal to the sum of all the quantity
      linked to its procurement must be ignored. In this way, when a SO line has
      an Ordered Qty equal to 0 in a SO, all the other lines can be processed like
      in 8.0
      
      opw:669200
      1f081bed
    • Denis Ledoux's avatar
      [FIX] event_sale: event tickets domain in sale order line · 4c7e33fd
      Denis Ledoux authored
      From saas-6, setting `0` as maximum available seats
      means there is an unlimited amount of tickts that
      can be sold, as stated in the help message of the field:
      ```
      Define the number of available tickets. If you have too much registrations you will
      not BE able to sell tickets anymore. Set 0 to ignore this rule set as unlimited.
      ```
      
      This domain is the same domain used than in
      the QWeb views of `website_event_sale`.
      
      opw-669355
      4c7e33fd
    • Denis Ledoux's avatar
      [FIX] mail: specific message subscribe · 26d6e838
      Denis Ledoux authored
      `write` expects a `dict` for the `values` argument,
      `part[record.id]` is a list of commands to add new
      followers.
      
      See the returned variable `specific` of the method
      `_add_follower_command` in `mail_followers.py`.
      
      Surrounding `part[record.id]` with a `dict` with
      `message_follower_ids` has probably been
      forgotten by oversight.
      
      `gen` and `part[record.id]` have actualy the same
      syntax, and the `write` done with these variables
      should therefore be called the same way.
      
      opw-669376
      26d6e838
    • Aaron Bohy's avatar
      [FIX] mail: followers: can't access res.partner case · 26f1d756
      Aaron Bohy authored
      When the user can't read the model res.partner, former code tried to determine
      whether or not the user was follower of the document. This was wrong for three
      reasons.
      
      First, it performed an RPC to get the partner_id of the current user, but this
      info is already stored in the session so the RPC was useless.
      Second, the partner_id isn't helpful to know if the user is a follower because
      everything we have is the follower_ids, which aren't ids of the res_partner
      model, but ids of the mail_follower model (compare apples and oranges...).
      Third, we anyway didn't use that information at all as the button indicating
      whether or not the user is a follower wasn't displayed.
      
      This rev. simply removes that useless RPC and only displays the count of
      followers as previously.
      26f1d756
Loading