An error occurred fetching the project authors.
- 18 Feb, 2013 1 commit
-
-
Julien Muchembled authored
... instead of relying on automatic migration. This fixes TestCMFActivity.test_connection_sortkey on Zope 2.13
-
- 28 Sep, 2012 1 commit
-
-
Sebastien Robin authored
-
- 23 Aug, 2012 4 commits
-
-
Rafael Monnerat authored
Sometimes on configuration product-config can be defined but promise-path and site id isn't, like for example when some instance use DeadlockDebugger.
-
Łukasz Nowak authored
Whitespaces shall be encoded with %digit
-
Romain Courteaud authored
-
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.
-
- 20 Jun, 2012 1 commit
-
-
Leonardo Rochael Almeida authored
Also, use local imports of itools where this is still necessary, and remove all mention of itools from ERP5 code.
-
- 03 May, 2012 1 commit
-
-
Julien Muchembled authored
They duplicate [gs]etDefaultActivateParameterDict on ActiveObject.
-
- 21 Mar, 2012 1 commit
-
-
Arnaud Fontaine authored
-
- 14 Mar, 2012 1 commit
-
-
Arnaud Fontaine authored
-
- 12 Mar, 2012 2 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
- 07 Mar, 2012 9 commits
-
-
Arnaud Fontaine authored
Also, declare ERP5Site.getVersionPriorityNameList() as protected rather than private for views.
-
Arnaud Fontaine authored
This is similar to portal skins priority, except that versions and priorities are defined on ERP5Site (as 'VERSION | PRIORITY' where PRIORITY is a float) as there is not one Folder for each version in contrary to portal skins. On the Business Template itself, versions and priorities can be defined like 'VERSION | PRIORITY' or simply 'VERSION' (where PRIORITY is assumed to be 0.0). Upon installation, it will be merged into ERP5Site property in descending order (by priority first and then by version for versions with the same priority).
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
An appropriate Python package is created in erp5.component.document. erp5.component.document.COMPONENT_REFERENCE is just an alias for erp5.component.document.VERSION.COMPONENT_REFERENCE where VERSION is the version with the highest priority (as defined by priority property on ComponentTool) where the component is available.
-
- 17 Oct, 2011 1 commit
-
-
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
-
- 26 Jul, 2011 1 commit
-
-
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.
-
- 19 Jul, 2011 1 commit
-
-
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.
-
- 22 Jun, 2011 1 commit
-
-
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.
-
- 31 Mar, 2011 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44836 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 30 Mar, 2011 1 commit
-
-
Julien Muchembled authored
This fixes several issues: - Some classes like XMLObject were outside Products.ERP5Type.Document and there were not migrated. - Persistent migration using _delOb/_setOb does not work with mount points. A new Base.migrateToPortalTypeClass method is also provided to migrate objects persistently. Note however that migration of HBTrees requires additional work, using PickleUpdater method. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44780 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 25 Feb, 2011 2 commits
-
-
Jérome Perrin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43739 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Nicolas Delaby authored
Make it explicit and configurable git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43728 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 23 Feb, 2011 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43620 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 19 Feb, 2011 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43490 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 18 Feb, 2011 1 commit
-
-
Julien Muchembled authored
- Most property sheets are in a new 'erp5_property_sheets' business template, which is installed first (even before erp5_core). - Bootstrap is done by fetching the few required objects directly from core BT. - Properties/constraints/categories stores the reference inside the id (instead of 'default_reference'), so that BT is exported with nice filenames. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43482 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 08 Feb, 2011 1 commit
-
-
Nicolas Dumazet authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43146 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 04 Feb, 2011 1 commit
-
-
Nicolas Dumazet authored
addERP5Tool might be clever now, and avoids recreating portal_activities if it already exists, but the line just after should *not* be run if the tool already exists, or else we simply clear all activities generating during BT5 install. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@43012 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 03 Feb, 2011 1 commit
-
-
Nicolas Dumazet authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42975 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 02 Feb, 2011 1 commit
-
-
Nicolas Dumazet authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42918 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 01 Feb, 2011 2 commits
-
-
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
-
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
-
- 19 Jan, 2011 1 commit
-
-
Nicolas Dumazet authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42437 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 14 Jan, 2011 1 commit
-
-
Nicolas Dumazet authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42325 20353a03-c40f-0410-a6d1-a30d3c3de9de
-