Skip to content
Snippets Groups Projects
  1. Jul 08, 2013
  2. Jul 07, 2013
    • Launchpad's avatar
      Launchpad automatic translations update. · c0119a87
      Launchpad authored
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130706061750-b7mm65zaln6pacmc
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130707055412-bb9fnxig7ss4pugc
      c0119a87
  3. Jul 05, 2013
  4. Jul 04, 2013
  5. Jul 03, 2013
    • Olivier Dony's avatar
      [FIX] ir.ui.view: properly validate newly created inheriting views · eae2321c
      Olivier Dony authored
        
        When a new inheriting view is imported during a module
        installation, it is validated thanks to the _constraints
        on the ir.ui.view model. However the validation uses
        a rather convoluted system for validating the whole
        view tree at once (root view + all inherited changes)
        while only taking into account the views that belong
        to modules that are currently loaded.
        
        This complicated system is necessary to be able to
        operate on-the-fly at any point during the registry
        loading/initialization.
        
        Now because _constraints are checked during create()
        this particular validation happens *before* the
        external ID (ir.model.data entry) of that new view
        can be created (it obviously needs to wait until
        the view record is inserted). As a consequence the
        view validation cannot determine the module to
        which that new view belongs, and was erroneously
        ignoring it.
        Changing the view filtering to also include views
        from unknown modules fixes this transient problem,
        and also means that manually created inherited
        views will be validated during module init too.
      
      bzr revid: odo@openerp.com-20130703215704-x732bepiifvf4g3n
      eae2321c
  6. Jul 05, 2013
  7. Jul 03, 2013
  8. Jul 02, 2013
  9. Jul 01, 2013
    • Olivier Dony's avatar
      [FIX] procurement: background procurement scheduler should be working in batch... · 9b6f5dca
      Olivier Dony authored
      [FIX] procurement: background procurement scheduler should be working in batch mode, with one transaction per order
      
      A programming error during an older refactoring lead to
      the scheduler working with a single monolithic transaction.
      This could cause unnecessary resource contention, plus
      undesired rollback of all previous operations in the event
      of an exception during scheduling.
      
      bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c
      9b6f5dca
  10. Jul 02, 2013
  11. Jun 28, 2013
  12. Jun 27, 2013
  13. Jun 26, 2013
  14. Jun 24, 2013
    • Denis Ledoux's avatar
      [FIX]account: fix of sxw of account_print_invoice, which was using... · f4ac9a07
      Denis Ledoux authored
      [FIX]account: fix of sxw of account_print_invoice, which was using o.address_invoice_id.partner_id instead of o.partner_id
      
      bzr revid: dle@openerp.com-20130624145856-vz0d8oezyqoj7gou
      f4ac9a07
    • Martin Trigaux's avatar
      [MERGE] [FIX] OPW 590066 account: remove accounting information lines from Journal items · db6e3bb4
      Martin Trigaux authored
      bzr revid: mat@openerp.com-20130624124418-r6fkvaokbfn3dvbg
      db6e3bb4
    • Xavier Alt's avatar
      [MERGE] [FIX] l10n_be_invoice_bba: correctly create bba reference when creating an invoice · 58badffa
      Xavier Alt authored
        When creating an invoice from another object (sale: invoice from sale order
        line, sale: invoice on delivery order, ...) we have to make sure that newly
        created invoice respect partner's default ``communication type``, and
        accordingly generate a new BBA if required and none provided.
      
      lp bug: https://launchpad.net/bugs/1135710 fixed
      
      bzr revid: xal@openerp.com-20130624083322-h3h4h8nn876585m3
      58badffa
    • Xavier Morel's avatar
      [FIX] evaluation context structures not being round-tripped through eval · 11a0ece5
      Xavier Morel authored
      JS objects are converted to py.object when passed in through the
      evaluation context. py.object are not serializable by default (because
      that doesn't really make sense), which breaks when the input is
      intended as a dict and returned (e.g. o2m values, which are triples of
      (int, int?, dict?)).
      
      Intuitively, JS objects passed as part of the context should be mostly
      JSON-ish and thus dicts, but that turns out not work work as some
      addons use attribute accesses within contexts (e.g. parent.access in
      account/account_invoice_view.xml)
      
      => Temporarily solve by converting raw js objects to an "attributed
      dict" which acts as both a dict and an object and can be converted to
      JSON.
      
      Ideally, py.js should provide for a pluggable conversion, or should
      use an attributed mapping internally. See issues 21 and 23.
      
      lp bug: https://launchpad.net/bugs/1182101 fixed
      
      bzr revid: xmo@openerp.com-20130624055929-3rtkgqrp4o87pvau
      11a0ece5
    • Launchpad's avatar
      Launchpad automatic translations update. · e2c795e2
      Launchpad authored
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130622062509-09p9c2ue6lp31hfi
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130623055456-p4wd0c25eb7i07g1
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130624052601-ewqft8e70ql5qs27
      e2c795e2
    • Launchpad's avatar
      Launchpad automatic translations update. · 89bc6e5e
      Launchpad authored
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130622062505-fobx7ncp6bkpouyt
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130623055452-s77jlu7z6kvjbdlz
      bzr revid: launchpad_translations_on_behalf_of_openerp-20130624052557-hsaix5c3fu6opbva
      89bc6e5e
  15. Jun 21, 2013
Loading