- 03 Apr, 2018 1 commit
-
-
Romain Courteaud authored
-
- 30 Mar, 2018 17 commits
-
-
Romain Courteaud authored
Reduce duplicated code.
-
Romain Courteaud authored
Use the hardcoded https://validator.erp5.net service This service is installed with: https://lab.nexedi.com/nexedi/slapos/tree/master/software/htmlvalidatorserver
-
Romain Courteaud authored
-
Nicolas Wavrant authored
Add "Post Modules", a serie of modules whose purpose is to track exchanges in/out of ERP5. Currently, users write Mail Messages (usually as a HTML content), and then send the Mail Message. The RFC5322 version of the email (what is given to MailHost and sent over the network) is generated on the fly and never stored anywhere. About Letter, no output is generated. It means that exchanges are not tracked, and if an Event is sent 2 times, we don't know their exact content on both times. Posts have the purpose to fix this issue, by creating objects storing the content of the sent Events **exactly as they are transmitted out of ERP5**. In exemple, sent Mail Messages will be converted to a multi-part message, stored as a Internet Message Post, which content will be transmitted as such to MailHost. For Letters, their content can be processed (by erp5_corporate_identity for exemple), then converted to PDF, and stored as Letter Post. We can then imagine actions/alarms to gather all exportable Letters Posts and mail them to a printer. Posts follow their own workflow, shared in between all post types, which allow to track which posts are in the sending queue, which have been sent and which have been received. It must be easy to know when an event has been sent several time, and retrieve the content of each of these sendings. Design of the post modules/workflow should also allow an easy customization (for exemple, we may want to send all emails by bulk, instead of 1 by 1, in order to set up mass-emailing policies). /reviewed-on nexedi/erp5!532
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
This mixin contains all the methods returning values based on the mail message itself contained in the data property of the EmailDocument.
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
erp5_crm: display standard preview on Mail Message only if internet_message_post_module isn't installed
-
Nicolas Wavrant authored
The attachment field now uses the property aggregate_document_title of Event.
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
It will be used to differenciate attachments from Mime Post.
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
-
Jérome Perrin authored
This should address two issues: 1. Allow using a custom python interpreter where all eggs dependencies would already be installed. 2. The test names did not have stable name, because they were the full path of the folder, which varies from one test node to another. This depends on changes in the profile done in nexedi/slapos!309 . This changes the internals of `EggTestSuite` so other tests reusing it ( I think we only have [`deploy-test`](https://lab.nexedi.com/nexedi/slapos/blob/41191a29cd16af13b2667d1979f35628c6065fde/software/erp5testnode/testsuite/deploy-test/runTestSuite.py#L151-154) ) will have to be updated once a new `erp5.util` is released. @luke I guess this won't be a problem and this would allow to fix that second issue for deploy test as well, so I did not consider being backward compatible here. /cc @rafael @alain.takoudjou /reviewed-on nexedi/erp5!619
-
- 29 Mar, 2018 5 commits
-
-
Tristan Cavelier authored
Move Base_checkCloneDocumentPermission beside Base_createCloneDocument
-
Nicolas Wavrant authored
As blobs aren't serializable
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
-
Tristan Cavelier authored
-
- 27 Mar, 2018 17 commits
-
-
Tristan Cavelier authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
Drop usage of cellpadding, cellspacing, border.
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
2nd try
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Tomáš Peterka authored
-
Vincent Pelletier authored
Calling these can break catalog by not caring about concurrent indexation activities. Even non-restricted code should not call these, but: - they cannot be reliably renamed, as there exist activity dependencies looking for these exact names (which is a bad practice on its own) - there is no simple access control mechanism for non-restricted code So rely on developer discipline instead.
-
Vincent Pelletier authored
These methods must not be called synchronously: - they can break catalog by not being careful enough about other reindexations which may happen in parallel. See the serialization_tag mechanism for more. - indexation gets executed in the security context of the user causing the call, which may lead to an indexation result different from what happens when indexation happens with an all-accesses user. Also, simplify a few scripts while doing so.
-
Vincent Pelletier authored
The rationale behind this change is to cover the case of sub-documents modified as part of acquired setters (ex: subordination on Person which actually sets it on a Career subdocument, or address on Person, etc). As these value can be passed to newContent (and passed on to constructInstance) along with immediate reindexation request, caller may expect these to be also indexed.
-