An error occurred fetching the project authors.
  1. 19 Mar, 2014 1 commit
  2. 14 Mar, 2014 2 commits
  3. 26 Feb, 2014 1 commit
  4. 19 Feb, 2014 1 commit
  5. 24 Jan, 2014 1 commit
  6. 23 Jan, 2014 2 commits
  7. 16 Jan, 2014 3 commits
  8. 04 Jan, 2014 1 commit
  9. 24 Dec, 2013 3 commits
  10. 18 Dec, 2013 1 commit
  11. 16 Dec, 2013 1 commit
  12. 05 Nov, 2013 1 commit
  13. 30 Oct, 2013 1 commit
  14. 25 Oct, 2013 2 commits
  15. 15 Oct, 2013 2 commits
  16. 07 Oct, 2013 3 commits
  17. 23 Sep, 2013 1 commit
  18. 16 Sep, 2013 2 commits
  19. 11 Sep, 2013 2 commits
    • Boris Kocherov's avatar
    • Tatuya Kamada's avatar
      Inventory: Change the default inventory parameter for Inventory indexing. · 22fea21f
      Tatuya Kamada authored
      Before:
      
      default_inventory_calculation_list = ({"inventory_params" :
                                              {"node" : self.getDestination(),
                                               "group_by_sub_variation" : 1,
                                               "group_by_variation" : 1,
                                               "group_by_resource" : 1,
                                               }
                                               ..
      
      After:
      
      default_inventory_calculation_list = ({"inventory_params" :
                                             {"section": self.getDestinationSection(),
                                              "node" : self.getDestination(),
                                              "group_by_sub_variation" : 1,
                                              "group_by_variation" : 1,
                                              "group_by_resource" : 1,
                                               }
                                              ..
      
      This is because Inventory_view of erp5_trade has both 'section' and 'node'
      fields, so users can input both values, but due to the old default parameter,
      the section will be ignored for inventory indexing. This is inconsitent.
      22fea21f
  20. 10 Sep, 2013 4 commits
  21. 09 Sep, 2013 2 commits
    • Arnaud Fontaine's avatar
      ZODB Components: Fix bootstrap of migrated bt5s. · aed4f303
      Arnaud Fontaine authored
      * Upon bt5 installation, install portal_type* items before bt5 {Document,
        Extensions...} as corresponding Portal Type are required once they have been
        migrated to ZODB Components.
      
      * Likewise portal_{property_sheets, types}, portal_components must be created
        automatically *before* installing any bt5. This is required when Products
        will be migrated but also for bt5 items before bootstrapping erp5_core bt5.
      
      * Set Permissions in ComponentTool instanciation and revoke all permissions,
        then allow only some of them for security sake.
      
      * When creating ERP5 site with unit tests, add ERP5TypeTestCase to Developer
        Role ASAP so that there is no Permission issue when installing bootstrap bt5
        and test bt5s containing ZODB Components.
      aed4f303
    • Arnaud Fontaine's avatar
      ZODB Components: Upon migration, Workflow History of ZODB Components must be kept. · dce6323f
      Arnaud Fontaine authored
      Also, upon installation of bt5s, install WorkflowItem before Components as it
      is needed to restore history.
      
      Another solution would have been to validate() ZODB Components automatically
      upon bt5 installation but it would mean losing 'modified' state information
      and also imply that *all of them* will be validated even if a developer wants
      to publish non-validated ZODB Components.
      dce6323f
  22. 05 Sep, 2013 1 commit
  23. 29 Aug, 2013 1 commit
  24. 19 Aug, 2013 1 commit