An error occurred fetching the project authors.
  1. 19 Jul, 2011 1 commit
    • Leonardo Rochael Almeida's avatar
      temp object must not skip interaction on real one · e4cb0458
      Leonardo Rochael Almeida authored
      Only prevent transition from running if it has actually run. If its guard
      prevents it from running, consider it still runnable in this transaction.
      
      This change doesn't help to skip the interaction on the real object if it's
      not forbidden on the temp one.
      e4cb0458
  2. 14 Feb, 2011 1 commit
    • Nicolas Dumazet's avatar
      fix wrong test that expected edit() to call the public setter. · 98bfee4f
      Nicolas Dumazet authored
      It happened sometime, with aq_dynamic, when a setter was overriden on the class
      itself, that setFoo was called on a edit(foo=bar), as class methods were taking
      priority over aq_dynamic-generated-setters.  Now, the correct behavior is back:
      edit(foo=bar) calls the private setter directly, and never the public setter.
      
      See "Workflow triggers and edit/_edit calling (or not) private or public
      setters" email for reference.
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43304 20353a03-c40f-0410-a6d1-a30d3c3de9de
      98bfee4f
  3. 07 Feb, 2011 1 commit
  4. 29 Oct, 2010 1 commit
    • Nicolas Dumazet's avatar
      fix test_security_defined_on_class after portal type classes changes · 1f851edf
      Nicolas Dumazet authored
      This test checks that wrapping a method in an interaction workflow adds
      security to the wrapped method, but that it does not override existing
      (class) security definition.
      
      To do so, a private method (doSomethingStupid) is added on Organisation
      document class. We really want to change the (static) document class here,
      not the portal type class: before portal type classes changes,
      ERP5Type.Document.Organisation.Organisation was a copy of the document
      ERP5.Document.Organisation.Organisation. After portal classes, the former
      is a portal type class, and it does not make sense in test logic to add
      a method on the portal type class.
      
      It is correct to change the import path to access the physical Document class.
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39652 20353a03-c40f-0410-a6d1-a30d3c3de9de
      1f851edf
  5. 07 Jan, 2010 1 commit
  6. 24 Nov, 2009 1 commit
  7. 30 Oct, 2009 1 commit
  8. 09 Oct, 2009 1 commit
  9. 01 Sep, 2009 1 commit
    • Julien Muchembled's avatar
      Do not call 'apply' on an existing 'security' attribute once the class is built · d3168976
      Julien Muchembled authored
      More generally, the 'security' attribute should not be used once the class is
      built, because the constructor of classes inherited from SimpleItem deletes it.
      This is currently tolerated in ERP5 because there is always CopyContainer that
      provides one, but it also means that CopyContainer.security is just a mix of
      attributes generated automatically on most classes.
      
      Previous code was equivalent to
        CopyContainer.security.declarePrivate('doSomethingStupid')
        CopyContainer.security.apply(Organisation)
      which is nonsense.
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28730 20353a03-c40f-0410-a6d1-a30d3c3de9de
      d3168976
  10. 12 May, 2009 1 commit
  11. 15 Oct, 2008 1 commit
  12. 14 Oct, 2008 1 commit
  13. 15 Apr, 2008 1 commit
  14. 29 Feb, 2008 1 commit
  15. 14 Jan, 2008 2 commits
  16. 29 Oct, 2007 1 commit
  17. 17 Sep, 2007 2 commits
  18. 31 Aug, 2007 1 commit
  19. 23 Mar, 2007 1 commit
  20. 15 Sep, 2006 1 commit
  21. 21 Jul, 2006 1 commit
  22. 22 May, 2006 1 commit
  23. 09 May, 2006 1 commit
  24. 25 Mar, 2006 1 commit
  25. 02 Mar, 2006 1 commit
  26. 18 Oct, 2005 1 commit
  27. 15 Oct, 2005 1 commit
  28. 14 Oct, 2005 1 commit
  29. 26 Sep, 2005 1 commit
  30. 23 Sep, 2005 1 commit
  31. 18 Jul, 2005 1 commit
  32. 04 Apr, 2005 2 commits