- 16 Apr, 2021 1 commit
-
-
Jérome Perrin authored
When rendering error page, the default header_title is computed in global_definitions and this is done by concatenating string:ERP5 (which is unicode) and the title of the portal (which is an UTF-8 encoded string), which causes an UnicodeDecodeError, because the portal title was decoded as ASCII. Because header_title is usually an UTF-8 encoded string, also use an UTF-8 encoded string for 'ERP5' default value.
-
- 15 Apr, 2021 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 14 Apr, 2021 9 commits
-
-
Xiaowu Zhang authored
See merge request !1395
-
Arnaud Fontaine authored
Revert "erp5_officejs: erp5_hal_json_style Skin is used and without it erp5_officejs cannot be installed." This reverts commit 1b706b6c. erp5_officejs depends erp5_web_renderjs_ui which in turn depends on erp5_hal_json_style.
-
Xiaowu Zhang authored
There is no such as thing as "Long Title" in erp5 There is "Title" and "Short Title"
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
-
Jérome Perrin authored
because this business template uses fields from erp5_trade field libraries
-
Jérome Perrin authored
-
Jérome Perrin authored
These fields were created when proxify action was broken. This re-exports the fields after using fixConsistency on them. see also nexedi/erp5!1352
-
- 13 Apr, 2021 6 commits
-
-
Kazuhiko Shiozaki authored
also add rel="noopener noreferrer" for security.
-
Kazuhiko Shiozaki authored
-
Vincent Pelletier authored
It seems this workfliow was created by copy-pasting event_workflow, without cleaning these variables up: they are used by a transition dialog on event_workflow but nothing on this workflow. Still, they are stored on every single document on every single transition, wasting resources. So remove them.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
erp5_jquery_sheet_editor: unset Accelerated HTTP Cache Manager configuration in intermediate template.
-
- 12 Apr, 2021 3 commits
-
-
Kazuhiko Shiozaki authored
-
Vincent Pelletier authored
-
Jérome Perrin authored
-
- 09 Apr, 2021 4 commits
-
-
Nicolas Wavrant authored
See merge request !1385
-
Nicolas Wavrant authored
-
Nicolas Wavrant authored
So different test suites can have a same named sequence without theme colliding with each other
-
Nicolas Wavrant authored
-
- 07 Apr, 2021 1 commit
-
-
Arnaud Fontaine authored
-
- 06 Apr, 2021 1 commit
-
-
Jérome Perrin authored
-
- 02 Apr, 2021 2 commits
-
-
Jérome Perrin authored
When installing the tested software failed, no test result lines have been created, this should have status FAILED.
-
Jérome Perrin authored
person reference contained the username, so test was also passing, but what we really want to test is that the username is in the mail body.
-
- 01 Apr, 2021 1 commit
-
-
Jérome Perrin authored
ee64d50c (patches/CookieCrumbler: update patch for CMF 2.3, 2019-09-09) introduced a NameError, getRequest was not imported.
-
- 31 Mar, 2021 3 commits
-
-
Jérome Perrin authored
All reports were properly including movements from the last day, except general ledger which were only including movements made without hours:minutes (at midnight). This was not a problem for manually entered transactions, which are usually made at 00:00 but when transactions are entered with hour:minutes they were not included.
-
Nicolas Wavrant authored
-
Jérome Perrin authored
BMP are not compressed and use more disk space than PNG. The trick is that ERP5 uses by default a quality of 75% on images ([this is default on propertysheet]) so we need to dump the image with maximum (100%) quality. Update also assertion message to not include the full base64 image in case of difference, use a short assertion message and save images in log folder. [this is default on propertysheet]: https://lab.nexedi.com/nexedi/erp5/blob/2f9b67fae3ac59955231d4191a34134ff1b6079a/product/ERP5/bootstrap/erp5_property_sheets/PropertySheetTemplateItem/portal_property_sheets/HtmlStylePreference/preferred_image_quality_property.xml#L56
-
- 30 Mar, 2021 1 commit
-
-
Jérome Perrin authored
When rendering reports, deferred style was only keeping request.other, but some places, like Products.ERP5Form.ListBox.ListBox.getParamDict read only in request.form, which caused different behaviours when rendering reports directly or in activities, because when rendering in activities request keys that the report dialog might have pushed were not preset in request. They were of course present when rendering the report directly, because this was the same request, so this lead to different behaviours wether reports were rendering in activities or directly, like we could observe in 7058ab6f (accounting: fix grouping option of GL when running in deferred mode, 2021-02-25) This change deferred style to properly propagate request.other and request.form in all activities of reports.
-
- 29 Mar, 2021 7 commits
-
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
-
Gabriel Monnerat authored
Calculate link to allow Nexedi developers access the ERP5 fields, forms and form actions from it. * erp5 form gadget handle links to access from and form action * label field gadget handle links to access field configuration, title and descriptions translations * page action handle all links to access workflows and portal type document * add generic function to merge action with raw actions by group * Add sample of action that allow uses access slideshow from ERP5JS
-
Jérome Perrin authored
ERP5 uses a mix of context.REQUEST and Products.ERP5Type.Global.get_request(), which now uses zope.globalrequest.getRequest(). CMFActivity reconstruct the original request before executing activity, so that the activity is executed with a request equivalent to the request at the time where the method was activated. For this, context.REQUEST was properly restored, but get_request()/globalrequest was only restored when the REQUEST had some Accept-Language header, so that it replays the language negociation for Localizer. With browser requests, I guess every browser pass an Accept-Language header ( according to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language all major browser support it), but within unit tests such header is not present. So this lead to activities with unit test requests being slightly different, because as they don't have Accept-Language, context.REQUEST was set, but the global request was not set, so they were running with two different requests in context.REQUEST and global request, leading to some problems for example with formulator fields.
-