- 08 Oct, 2018 5 commits
-
-
Jérome Perrin authored
/reviewed-on !760
-
Jérome Perrin authored
/reviewed-on nexedi/erp5!762
-
Ayush Tiwari authored
Also, update tests for notebook to check for Upload page
-
Ayush Tiwari authored
/reviewed-on nexedi/erp5!764
-
Ayush Tiwari authored
-
- 05 Oct, 2018 2 commits
-
-
Xiaowu Zhang authored
-
Tristan Cavelier authored
Fixes rendering when using Chameleon: ValueError: only strings can be translated, not: <ERP5Type.Message.Message for ...
-
- 04 Oct, 2018 10 commits
-
-
Ayush Tiwari authored
/reviewed-on !747
-
Xiaowu Zhang authored
/reviewed-on !765
-
Xiaowu Zhang authored
adjust font url
-
Xiaowu Zhang authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Vincent Pelletier authored
-
- 03 Oct, 2018 5 commits
-
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Jérome Perrin authored
Otherwise filling cache fail and it's never used.
-
Jérome Perrin authored
-
- 02 Oct, 2018 9 commits
-
-
Yusei Tahara authored
-
Jérome Perrin authored
/reviewed-on !759
-
Jérome Perrin authored
This reapplies parts of 9a84ef83 , but a different server side approach: * use portal_workflow API to count worklists * introspect workflow to build queries * use translated state in the query, trying to be a bit more user friendly. We could do for portal_type as well. This workarounds #20180907-24A654C a problem with queries generated by gadget worklist does not seem to support complex queries with multiple values ( local_roles: ['Assignor', 'Assignee'] ). This code generates queries: ``` ( ( local_roles: "Assignee" OR local_roles: "Assignor" ) AND portal_type: "Support Request" AND translated_simulation_state_title: "Opened" ) ``` where the previous version generated queries like: ``` ( portal_type: "Support Request" AND simulation_state: "validated" AND local_roles: ( "Assignee" OR "Assignor" ) ) ``` which did not match anything. Maybe because local_roles is handled differently in catalog
-
Jérome Perrin authored
This reverts commit 9a84ef83. Eventhough there's a delay due to cache, the default worklist implementation is efficient and worklist is translated.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Vincent Pelletier authored
These will be added by activity spawning mechanism: either "activate" or "recurseCallMethod".
-
Vincent Pelletier authored
Subsequent activities will produce an empty dictionary, causing inconsistencies in activity dependencies.
-
Vincent Pelletier authored
It is set in constructInstance from received activate_kw, but is then if ActiveObject.activate is not used - as is the case when reindexObject is made an alias of recursiveReindexObject (ex: ERP5.Document.Delivery), as the latter calls recurseCallMethod which uses ActivityTool.activateObject which (purposefully, visibly) ignores getDefaultActivateParameterDict (unlike ActiveObject.activate). Also, do not step on activate_kw, for readability.
-
- 01 Oct, 2018 9 commits
-
-
Jérome Perrin authored
Also: * don't immediate reindex, this is a coding crime * don't search catalog by ID, use direct module access
-
Jérome Perrin authored
To make it easier to test worklists and dashboard. SR-15 Crashed! is Opened SR-16 Boom! is Suspended SR-17 Done is Closed
-
Jérome Perrin authored
Because worklists tests expect to run with ERP5TypeTestCase user, and this test uses another user.
-
Ayush Tiwari authored
-
Ayush Tiwari authored
Partial revert from 2f121c19
-
Thomas Gambier authored
/reviewed-on nexedi/erp5!757
-
Jérome Perrin authored
-
Jérome Perrin authored
This is not used in this interface
-
Jérome Perrin authored
now that we have ERP5 Login, reference is just reference.
-