1. 20 Sep, 2016 1 commit
  2. 19 Sep, 2016 1 commit
  3. 16 Sep, 2016 1 commit
  4. 15 Sep, 2016 3 commits
  5. 14 Sep, 2016 1 commit
  6. 02 Sep, 2016 2 commits
  7. 31 Aug, 2016 4 commits
  8. 29 Aug, 2016 1 commit
  9. 24 Aug, 2016 2 commits
  10. 23 Aug, 2016 3 commits
  11. 22 Aug, 2016 5 commits
  12. 19 Aug, 2016 1 commit
  13. 18 Aug, 2016 1 commit
  14. 11 Aug, 2016 1 commit
    • Rafael Monnerat's avatar
      PerformanceTests: Update to the new hardware · 5a7536ce
      Rafael Monnerat authored
        Performance tests were reconfigured on a new hardware, which is slower them
        the previous one. So this commit move the values to the new hardware based on
        the results after few days of result.
  15. 10 Aug, 2016 2 commits
    • Sebastien Robin's avatar
      order builder: improve stock optimisations to handle several nodes · b1798654
      Sebastien Robin authored
      This is very helpful when a warehouse is splitted into multiple
      stock points.
      Also avoid returning no stock optimisations if no date could be
      found in future.
    • Sebastien Robin's avatar
      ERP5Type.dynamic: show up failures in __getattribute__ of lazy_class · d032411c
      Sebastien Robin authored
      If for some reasons loadClass was not working, it was failing totally
      silently without any log. If there is any unexpected error in loadClass,
      this ended up for example having some tests failing with :
      RuntimeError: Malformed property definition <persistent broken
      erp5.portal_type.Acquired Property instance '\x00\x00\x00\x00\x00\x00\x12\xb5'>
      on /erp5/portal_property_sheets/SimpleItem
      While only this was displayed in logs :
      ERP5Type/dynamic/lazy_class.py", line 350, in loadClass
          class_definition = generatePortalTypeClass(site, portal_type)
      AttributeError: __of__
      Which was totally unrelated to the real problem.
      So a silent initial error was the source of later unrelated errors, making
      it very difficult to find the initial source of problem.
      So make sure we have logs as soon as we are not able to load a class.
  16. 09 Aug, 2016 2 commits
  17. 04 Aug, 2016 2 commits
  18. 02 Aug, 2016 3 commits
    • Ayush Tiwari's avatar
      erp5_standard_property: Add select_variable property for Standard Property object. · 3cf4d7f7
      Ayush Tiwari authored
      This change solves the error which one gets while trying to access properties
      Form for an ERP5 object having one or more of its property of type 'selection'
      or 'multiple selection'.
      For example: If you try to access property form for any portal_type objects,
      you'll get an error : "'select_variable' is not defined". This is because of the
      absence of the property 'select_variable' for the property of type multiple selection,
      which in case of portal_type object is 'Property Sheet List'.
      This is helpful for ERP5 views/forms which displays selection or multiple selection
      type object.
    • Ayush Tiwari's avatar
    • Ayush Tiwari's avatar
      ERP5 Subcategory: Remove '_'(underscore) from 'multiple_selection' subcategory... · 1075a315
      Ayush Tiwari authored
      ERP5 Subcategory: Remove '_'(underscore) from 'multiple_selection' subcategory in elmentary_type category.
      Subcategory 'multiple_selection' has been renamed to 'multiple selection' to maintain consistency.
      Earlier, whenever a new StandardCategory object was created with property_type 'multiple selection',
      one needed to change the elementary type explicilty to use it to generate property setters and getters.
      The example for this can be seen from this commit:
      After this change, in the view, property type field couldn't recognize the property and displays
      (???multiple selection).
      Also, everywhere in erp5, list_types do mention 'multiple selction' and not 'multiple_selection'.
      So, its better to maintain consistency in naming the subcategory.
  19. 27 Jul, 2016 1 commit
  20. 25 Jul, 2016 1 commit
    • Arnaud Fontaine's avatar
      ZODB Components: Fix bootstrap issue. · 5ba7e6fa
      Arnaud Fontaine authored
      When a Property Sheet with a ScriptConstraint (whose Document is a ZODB
      Component) was added to Memcached Tool: Document Component was partially
      loaded with no Property Sheet yet (and thus without the accessors needed
      to import ScriptConstraint ZODB Component) and ScriptConstraint Document
      was considered not available.
  21. 15 Jul, 2016 2 commits