An error occurred fetching the project authors.
- 07 Mar, 2012 40 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
The only purpose of having Interaction Workflow defined on ComponentTool _setObject and _delObject was for BusinessTemplate installation and uninstallation, however the reset was also triggered when a new draft Component was being added. Instead, perform the reset in BusinessTemplate DocumentTemplateItem.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
This new Role is defined only on portal_components and users can be only added to this Role through editing zope.conf. Also, add a Permission for reset as this role is not available outside of portal_components and is still useful for Workflows for example.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Also, Rename *MigrateAllComponentFromFilesystem to *MigrateSourceCodeFromFilesystem.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
This avoids having two interaction workflow for resetting dynamic classes and modules.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Instead, use savepoint which avoids triggering interaction workflows.
-
Arnaud Fontaine authored
Also, set _archive properly for ZODB Document and Extension.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Add missing version in Component document_id for testBusinessTemplate (087ef32b908c9b384f5769fa2375c3202eff2ed5).
-
Arnaud Fontaine authored
This reverts commit deb7e37e7690d50a6dc1e9aab05f4a7099973287 which introduced a regression (test_BusinessTemplateWithDocumentPropertySheetMigrated failed). Conflicts: product/ERP5/Document/BusinessTemplate.py
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
These tests also check whether recordable properties are properly set and cleared.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Checking the validation state is not enough as the validated value (save through RecordablePropertyMixin) should never be overriden even when a Component in modified state is saved and still contain errors.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
This allows to check consistency of reference and version as well (through PropertyRecordableMixin rather than fiddling with the workflow history). Also, split up state and error message into two separate fields.
-
Arnaud Fontaine authored
Errors may occur if in the same transaction a Component is created and another one depending upon the former...
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Instead, reset it everytime because after all, contentValues() is rather fast even with 1000 objects.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Add Business Template action to import Document and Extensions automatically after giving the version. Migration is now performed at Business Template level as it makes more sense rather than on Component Tool which would require specifying the target Business Template to update Document Template Item and Extension Template Item.
-