An error occurred fetching the project authors.
  1. 11 Jun, 2013 1 commit
  2. 10 Jun, 2013 2 commits
  3. 21 May, 2013 2 commits
  4. 20 May, 2013 1 commit
  5. 22 Apr, 2013 2 commits
    • Julien Muchembled's avatar
      CMFActivity: move message serialization code to Message class · ee2edadb
      Julien Muchembled authored
      Later, we might want to do more processing after loading, or before dumping,
      accessing private Message data.
      ee2edadb
    • Julien Muchembled's avatar
      CMFActivity: remove non-executable message state (-3) · e47f2923
      Julien Muchembled authored
      When an object is deleted, higher level code used to flush its messages (without
      invoking them). However, a concurrent and very long transaction may be about to
      activate such an object, without conflict. We already experienced false -3
      errors that could prevent other messages to be validated.
      
      Because there is no efficient and reliable way to flush absolutely all messages,
      messages on deleted objects are now ignored and deleted without any email
      notification. There's only a WARNING in logs. But for performance reasons,
      there's still a flush on object deletion.
      
      To simplify code, messages that went to -3 for other reasons, like a
      non-existing method, now go to -2. In fact, this was already the case for
      grouped messages.
      
      In case that a path is recycled, it may still be possible for a message to be
      executed on a wrong object (the new one), instead of being ignored (because the
      activated object was deleted). So in such scenario, developer should make sure
      not to delete an object that may be activated in a concurrent transaction.
      If the original object has an OID at the moment it is activated, an assertion
      will make sure the message is not executed on another object.
      e47f2923
  6. 28 Dec, 2012 3 commits
  7. 17 Dec, 2012 1 commit
  8. 26 Nov, 2012 1 commit
  9. 24 Oct, 2012 1 commit
  10. 03 Jul, 2012 1 commit
  11. 02 Jul, 2012 1 commit
  12. 20 Jun, 2012 1 commit
  13. 07 Jun, 2012 1 commit
  14. 02 Jun, 2012 1 commit
    • Kazuhiko Shiozaki's avatar
      use UnrestrictedMethod's super user instead of ad-hoc SUPER_USER. Squashed commit of the following: · 4b16e1dd
      Kazuhiko Shiozaki authored
      commit 2ba8fb59b67cda4a35bda5ee809ac0dd6af40d84
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 23:26:30 2012 +0200
      
          if the activity is called by super user, it should be invoked with the same permission as UnrestrictedMethod.
      
      commit f63c2e8625934d0a5a056e933f4c7215098bfa1b
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 15:58:41 2012 +0200
      
          use UnrestrictedMethod's super user instead of ad-hoc SUPER_USER.
      
      commit 965460b092967bc3ada3ee7268e1f942fc770efd
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 15:57:45 2012 +0200
      
          security query for super user should be simply empty.
      
      commit 6d519b78f52f1a631d6663ee5594ae92a0730cc3
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 15:37:33 2012 +0200
      
          support both ERP5Security's SUPER_USER and UnrestrictedMethod's super user.
      
      commit 21431518b821a5e2756caad5393fc746bed79d36
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 15:32:45 2012 +0200
      
          make sure that SUPER_USER can access the object explicitly, that can be required with erp5_web.
      
      commit 63279ac74cbb40e520da36571927bfdee5af5e05
      Author: Kazuhiko Shiozaki <kazuhiko@nexedi.com>
      Date:   Fri Jun 1 15:27:00 2012 +0200
      
          use UnrestrictedMethod instead of ad-hoc SUPER_USER, still keeping SUPER_USER for compatibility.
      4b16e1dd
  15. 23 Apr, 2012 1 commit
  16. 06 Apr, 2012 1 commit
  17. 28 Dec, 2011 2 commits
  18. 23 Dec, 2011 1 commit
  19. 19 Oct, 2011 2 commits
  20. 17 Oct, 2011 2 commits
    • Julien Muchembled's avatar
      Simplify code by using some new Python syntax · 9cd33ca4
      Julien Muchembled authored
      - PEP 308: Conditional Expressions
      - PEP 341: Unified try/except/finally
      - PEP 343: The ‘with’ statement
      9cd33ca4
    • Julien Muchembled's avatar
      Drop support for Zope 2.8 · 48212534
      Julien Muchembled authored
      Checked following occurrences in comments:
      - "Python 2.[456]"
      - "Zope 2.[891]"
      - "BBB"
      - "BACK"
      
      Checked uses of:
      - email, hashlib, numpy & tarfile (modules)
      - ImportError
      - string.Template
      - suppress_events (parameter of _setObject)
      
      Excluded:
      - some forked modules (MailTemplates, PortalTransforms...)
      - some i18n compatibility code
      48212534
  21. 29 Aug, 2011 1 commit
  22. 09 Aug, 2011 1 commit
  23. 02 Aug, 2011 3 commits
  24. 01 Aug, 2011 2 commits
  25. 22 Jul, 2011 1 commit
  26. 08 Feb, 2011 1 commit
  27. 02 Feb, 2011 1 commit
  28. 01 Feb, 2011 1 commit
    • Nicolas Dumazet's avatar
      Last chunk of portal type classes / zodb property sheets. · d02ba206
      Nicolas Dumazet authored
      After this, all ERP5 objects become instances of portal type classes
      
      Preferences:
      * all the trickery for preferences is gone and is handled by a specific
        accessor holder holding all preference methods
      
      Property holders
      * our Base.aq_portal_type property holders are not used anymore:
        the "property holder" becomes the portal type class itself and the
        set of accessor_holder classes in the mro of the portal type class:
        portal-type-specific methods are on the portal type class, while
        portal-type-independant method are put on the accessor holder ancestors
      * the portal type meta class now also inherits from "PropertyHolder" to
        provide the same introspection interface and methods.
        (In the future this class / interface will need to be refined)
      
      Bootstrap/migration:
      * bootstrapping/migration from older instances: provide with code able to
        import XML from ERP5/bootstrap/ to load necessary tools from almost any
        instance state
      * migrate in BusinessTemplate installation code all non-portal type classes
        objects to portal type classes
      * Change the way Tools are installed when creating a site, so that we create
        directly portal type classes objects instead of Documents
      
      Accessors:
      * add a generatePortalTypeAccessors method on the portal type class to generate
        portal-type-specific accessors
      * associate BaseAccessorHolder to all portal type classes to contain
        all common category related accessors
      * change the way workflow methods are generated to bind them directly on
        the portal type class
      * disable Base._aq_dynamic (while still keeping its code for debugging and
        reference, this can be cleanup up later)
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42902 20353a03-c40f-0410-a6d1-a30d3c3de9de
      d02ba206
  29. 12 Jan, 2011 1 commit