- 11 Jul, 2024 40 commits
-
-
Romain Courteaud authored
erp5_web_renderjs_ui: filter action panel to only show meaningful actions in the context of the web site
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
only Assignee/Assignore can validate Project
-
Romain Courteaud authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
Nothing uses redirect_url, so do not bother setting it.
-
Vincent Pelletier authored
For consistency with what is being allowed in the Restricted monkey-patch.
-
Titouan Soulard authored
-
Jérome Perrin authored
Such errors are not retried with the retry adapter, so retry them directly.
-
Jérome Perrin authored
- the test was using wrong attribute and it was using DummyLocalizer, which breaks the site configuration. Fix the test and use mock - fix ods style not to translate untranslatable columns
-
Jérome Perrin authored
Page templates have a builtin translation system (with i18n:) and an "unicode conflict resolver", so it was not necessary to explicitly convert to unicode on python2 and this simplifies the transition to python3
-
Jérome Perrin authored
-
Jérome Perrin authored
This list was to cast the tuple, it can cause an AttributeError("'tuple' object has no attribute 'append'",) error when this branch is used. This is really an error code path, so that was unnoticed.
-
Jérome Perrin authored
introduce number:date-style for each of the "input_order" supported by DateTimeField, so that when exported to ODS we have the same input order as in html.
-
Jérome Perrin authored
so that we can test date time fields in listbox columns and listbox stat method easily.
-
Jérome Perrin authored
-
Jérome Perrin authored
With libreoffice5, float fields with input style 12.3% were correctly rendered as percentages without the need of an explicit number:percentage-style style, but with libreoffice7 it seems required, without this, a value of 2.05 is rendered as "2" instead of the expected "205%"
-
Jérome Perrin authored
Instead of duplicating the code for the case where a field value is rendered from a group (left, right etc) of the form and when the field value is rendered from a listbox editable field, reuse the macro also for fields from the form groups. Because fields from the form groups have top and bottom border, we introduce a new style prefix for these fields: "with_border_". Implementation note: We don't declare this new field in Base_getODSSupportedStylePrefixList, because we need to define the cell properties each time, so defining this dynamically is not really interesting.
-
Jérome Perrin authored
remove useless `field python: editable_fields.get(column_id, None)` tal:defines, the macro always documented `field` as required and all callers pass it. document that `style_prefix` is required
-
Jérome Perrin authored
This was set to 1.234,5 but erp5_ods_style does not support this style for now, so set it to a supported value for now so that we can progress with the testing of erp5_ods_style.
-
Jérome Perrin authored
Add a listbox with a figure editable field and a percentage editable field. These fields all have TALES to set precision from "precision" request key.
-
Jérome Perrin authored
Instead of using UnrestrictedMethod for the whole duration of discoverMetadata, revert to the original user permissions for the last part where we merge revision or change state, because we want this to fail when user is not allowed. This adjusts also the high level Base_contribute script to catch these errors and report them nicely to the user and while doing this some other problems were discovered and are also fixed. Some problems in ContributionTool.newContent were fixed, this was already trying to detect that a document is going to be merged and synchronously checked that this existing document can be replaced, to display an error to the user, but this part has two issues: - first it was using getMatchedFilenamePatternDict to find the document coordinates, but this method only supports preferred_document_filename_regular_expression capturing reference, but not the combination of node_reference and local_reference, so this was changed to use getPropertyDictFromFilename, which is what is actually used to compute the reference. - The second problem here was that this check was done with a standard restricted catalog search, but later mergeRevision uses an unrestricted search, so this was changed to use unrestricted catalog search to match mergeRevision The testing also revealed that the PDFDocument._setFile hack to clear the _content_information was only for _setFile, but not for _setData, so this was extended to _setData as well, so that a case where the PDF content is updated by setData also update content information.
-
Jérome Perrin authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-