1. 23 Aug, 2012 2 commits
    • Romain Courteaud's avatar
    • Romain Courteaud's avatar
      Add getPromiseParameter · 650c86f9
      Romain Courteaud authored
        Read external promise parameters.
      
        The parameters should be provided by an external configuration file.
        Location of this configuration file is defined in the zope configuration
        file in a product_config named as the path of the ERP5 site.
        Example if the site id is erp5:
          <product-config /erp5>
            promise_path /tmp/promise.cfg
          </product-config>
      
        The promise configuration is a simple ConfigParser readable file (a list of
        section containing a list of string parameters.
      
        getPromiseParameter returns None if the parameter isn't found.
      650c86f9
  2. 20 Jun, 2012 1 commit
  3. 03 May, 2012 1 commit
  4. 21 Mar, 2012 1 commit
  5. 14 Mar, 2012 1 commit
  6. 12 Mar, 2012 2 commits
  7. 07 Mar, 2012 9 commits
  8. 17 Oct, 2011 1 commit
    • 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
  9. 26 Jul, 2011 1 commit
    • Leonardo Rochael Almeida's avatar
      Automigration of ZTK site manager and translations · 0198e812
      Leonardo Rochael Almeida authored
      Sites migrated from Zope 2.8 don't have a configured component manager (a.k.a.
      SiteManager) and because of that, and its consequent lack of registration of
      the Localizer Message Catalogs as ITranslationDomain utilities, they don't
      perform translation correctly.
      
      Here we add a no-additional-cost migration by overriding the
      ObjectManager.getSiteManager() method, and automatically configuring the
      component manager, including translation domains.
      0198e812
  10. 19 Jul, 2011 1 commit
    • Rafael Monnerat's avatar
      Move Introspection Tool creation to instance bootstrap · 42446f0f
      Rafael Monnerat authored
      portal_instrospections is been used by SlapOS as a single place for detect
      lack of configuration (ie.: Missing bt5s, Missing memcache configuration...)
      
      Move to tnstance creation make things cleaner and it creates a standard
      place for information collection.
      42446f0f
  11. 22 Jun, 2011 1 commit
    • Julien Muchembled's avatar
      Remove most dangerous uses of 'chdir' syscall · ca182eef
      Julien Muchembled authored
      Because chdir/getcwd is global to the whole process, it is not thread-safe
      and may cause very serious bugs like data loss (for example when 'os.remove'
      or 'shutil.rmtree' are called with relative paths).
      
      There still remain uses of 'chdir' in ERP5 Subversion. A temporary quick change
      is done to reduce the probability of race conditions, but this should really be
      fixed.
      ca182eef
  12. 31 Mar, 2011 1 commit
  13. 30 Mar, 2011 1 commit
  14. 25 Feb, 2011 2 commits
  15. 23 Feb, 2011 1 commit
  16. 19 Feb, 2011 1 commit
  17. 18 Feb, 2011 1 commit
  18. 08 Feb, 2011 1 commit
  19. 04 Feb, 2011 1 commit
  20. 03 Feb, 2011 1 commit
  21. 02 Feb, 2011 1 commit
  22. 01 Feb, 2011 2 commits
    • 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
    • Nicolas Dumazet's avatar
      refine logging to avoid being pedantic when installing Sites. · d501c068
      Nicolas Dumazet authored
      I need some way to distinguish what happens when, later, an automatic migration
      happens, or when a Tool is not found: if this happens in a "normal" context,
      then logging should be very loud and verbose, as this is likely to crash your
      site.
      On the other hand, during bootstrap/setup, this is perfectly normal to miss
      some tools/modules, and we should not worry/log about it, or the NECESSARY
      logs will be quickly removed by developers tired of seeing "useless" logs...
      
      Better ideas that can work in a fresh site without workflows, portal types,
      or any advanced mechanism? I'm all ears.
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42877 20353a03-c40f-0410-a6d1-a30d3c3de9de
      d501c068
  23. 19 Jan, 2011 1 commit
  24. 14 Jan, 2011 1 commit
  25. 06 Jan, 2011 1 commit
  26. 21 Dec, 2010 1 commit
  27. 13 Dec, 2010 1 commit
  28. 06 Dec, 2010 1 commit