There are 2 shemes for VIRTUAL_URL_PARTS:
- 2-tuple with SERVER_URL and subpath
- 3-tuple with SERVER_URL, vh path and subpath
This code only supported the 2-tuple version, add support for the 3-tuple
version.
Allows Base to consistently override methods which are also overridden in
CMF where CMF implementation does not propagate the call to other
superclasses (ex: __before_publishing_traverse__ as of CMFCore-2.2.10).
Also allows simplifying several inheritance fixups.
Also, use super() instead of explicit resolution to Base.
Also: testBusinessTemplate: drop dead monkey-patch.
_getCopy is called during BusinessTemplate installation, but not the one
on this class. Which prevents reordering class inheritance between
SimpleItem and copy support classes.
So this is dead code which is not even explaining what it is trying to do
(ex: what document should it really not be called on ? what effect of this
method is undesired ? why is the method attached to this class ? why is
the cleanup restoring the original method, when this class does not have
this method to begin with but it merely gets it from its superclasses
which are re-inherited from by documents hence overriding it anyway ?,
and it is getting in the way of reordering class inheritance so it goes
away.
Also: ERP5Type.patches.CMFBTreeFolder: Fold patch onto ERP5Type.Core.Folder.
All ERP5UI-visible (hence needing to call allowedContentTypes) BTReeFolder2
instances should already inherit ERP5Type.Core.Folder, removing the need
for this monkey-patch.
Add missing ones from
RÈGLEMENT N° 2018-06 du 5 décembre 2018
LIVRE III – TENUE, STRUCTURE ET FONCTIONNEMENT DES COMPTES
Titre II – Nomenclature des comptes
Art. 320-2
/reviewed-on https://lab.nexedi.com/nexedi/erp5/merge_requests/1060
Example configuration:
from `portal_activities/manageLoadBalancing`:
in preferences:
This way when users request lots of reports we always have at least one activity node to process other activities. ( document_conversion is a fictional example at this point )
/reviewed-on https://lab.nexedi.com/nexedi/erp5/merge_requests/1057
This allow edit scripts or interactions to change the status message or
the status level using the same way as workflow scripts: script can set
the status text in request['portal_status_message'] and the status level
in request['portal_status_level'].
Note that part of this was already checked in accidentally in 97c40dcb
/reviewed-on https://lab.nexedi.com/nexedi/erp5/merge_requests/1052
When running test.erp5.testHalJsonStyle live tests, the same transaction
seems to be seeing two different users. This cause an incorrect cache hit
with the second user, which then retrieves values computed by & for the
first user.
Fix this by scoping the cache by user id, causing different cache entries
to be used.
Because this old editor field is deprecated in favor of the new gadget
based CKEditor, this is the minimum to get coding style test passing.
- disable pylint
- re-export with new extensions (.obj -> .bin)
All other Component modules must be kept alive during the REQUEST life (f523edc).
However, Unit Tests modules should be kept alive until it finished executing and
this may span accross multiple REQUESTS.
Issue found out when migrating testBusinessTemplate to erp5_core_test which was
failing as the module was GC'ed and its top-level variables were reset to None by
the interpreter.
Not migrated:
+ testERP5Site: Checks Site creation and overrides setUp().
+ testERP5TypeInterfaces: Verifies that classes implements the Interfaces they claim to implement.
=> Should probably be integrated into coding style Unit Tests and done
dynamically (MRO). Also, testERP5Interfaces imports code from that
Unit Test and requires non-core bt5 to be installed.
+ testInvalidationBug: To-do (failing).
+ testPredicate: testDomainTool, inheriting from TestPredicateMixin, should be rewritten to not
depend on erp5_apparel so that it can be moved to erp5_core_test.
Also, move manuallyInstallBusinessTemplate() and uninstallBusinessTemplate() from
ERP5TypeCommandLineTestCase to ERP5TypeTestCaseMixin as they are also used by
Live Unit Tests.
If set, all potentially long activities will be running on this family.
This can be used to prevent situation where all activities are no longer processed because all activity nodes are busy processing reports.
Valentin Benozillo