- 31 Jul, 2020 5 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
ERP5: Remove Capacity/GLPK: never used and broken since glpk Python module is not in ERP5 Software Release neither.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
* Properly override WebSite Document in erp5_web_shadir by creating a new version_priority. * Keep Web{Section,Site}TraversalHook in Product/ERP5/Document as these are not ERP5 objects. Also, add `kept_for_backward_compatibility_only` to importLocalDocument() to handle pattern where the Document class has been migrated but some code remains. * Move WebSection_get*PrecacheManifestList Python Script from bt5 not depending on erp5_web to erp5_web_renderjs as this is required by CodingStyleTest (WebSection being now in erp5_web).
-
- 29 Jul, 2020 5 commits
-
-
Julien Muchembled authored
When a first migration was reverted for any reason (e.g. ConflictError), the assertion failed because __setstate__ was not called yet to fix the class back to the old one.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
See merge request nexedi/erp5!1212
-
Vincent Pelletier authored
Fixes Active Process' "hasActivity" method when that document's uid is >2**32.
-
- 28 Jul, 2020 1 commit
-
-
Gabriel Monnerat authored
erp5_officejs_support_request_ui: Add begin date to the query when user click on "Last Month Activity" The filter when the user click on the "Last Month Activity" chart filter Support Request only by status (Submitted / Open / Suspended / Closed). So on the table "Recent updates", all the support request with the chosen status appear. There is no filter by "Begin Date" for the last 30 days, which is no coherent with the "Last Month Activity". => It should appear only the support request with the chosen status with a begin date < D - 30 days
-
- 24 Jul, 2020 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 23 Jul, 2020 3 commits
-
-
Xiaowu Zhang authored
See merge request !1214
-
Xiaowu Zhang authored
See merge request nexedi/erp5!1216
-
Xiaowu Zhang authored
-
- 22 Jul, 2020 7 commits
-
-
Lu Xu authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Base_viewDict does not produce valid html, showing the dict using showDict is enough
-
Jérome Perrin authored
- use html5 doctype - don't use i18n: tags where they are not processed - use class instead of id for elements that are repeated - remove Content-*-Type meta that are reported as invalid by nvu
-
Jérome Perrin authored
this class does nothing and does not seem used
-
Jérome Perrin authored
-
- 21 Jul, 2020 3 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
- 20 Jul, 2020 9 commits
-
-
Xiaowu Zhang authored
See merge request !1210
-
Xiaowu Zhang authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Jérome Perrin authored
Make `erp5_configurator_standard` use `erp5_configurator_standard_categories`. Since this is the business templates for standard (SME) configurator categories, it seems logical to install this business template when installing SME configuration. Before these changes, standard configurator was using a spreadsheet ( `standard_category.ods` ) to define the categories. Now this spreadsheet is almost empty, it only contain group and site that are custom and the configurated instance will install `erp5_configurator_standard_categories` business template. The main goal was to make generated configuration use unit conversion module instead of the obsolete quantity properties on quantity unit categories, but I thought it would make sense to use this `erp5_configurator_standard_categories` business template that is otherwise not used. See merge request !1172
-
Jérome Perrin authored
if for some reason an ERP5 document has some control characters in title of description and is exported in ODS/ODT, the export will fail with an etree error like this: Exception: Module Products.CMFActivity.ActivityTool, line 356, in __call__ result = method(*self.args, **self.kw) Module Products.ERP5Type.patches.PythonScript, line 179, in __call__ return self._orig_bindAndExec(args, kw, None) Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec return self._exec(bound_data, args, kw) Module Products.PythonScripts.PythonScript, line 344, in _exec result = f(*args, **kw) Module script, line 15, in Base_renderSimpleView - <PythonScript at /erp5/Base_renderSimpleView used for /erp5/sale_packing_list_module> - Line 15 report_data = getattr(context, deferred_style_dialog_method)(**params) Module AccessControl.ZopeGuards, line 369, in guarded_apply return builtin_guarded_apply(func, args, kws) Module AccessControl.ZopeGuards, line 391, in builtin_guarded_apply return func(*arglist, **argdict) Module Products.ERP5Form.Form, line 705, in __call__ return pt.pt_render(extra_context=extra_context) Module Products.ERP5OOo.OOoTemplate, line 484, in pt_render extra_context, request) Module Products.ERP5OOo.OOoTemplate, line 422, in renderIncludes xml_doc = etree.XML(text) Module lxml.etree, line 3192, in lxml.etree.XML (src/lxml/lxml.etree.c:78763) Module lxml.etree, line 1848, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:118341) Module lxml.etree, line 1736, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:117021) Module lxml.etree, line 1102, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:111265) Module lxml.etree, line 595, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:105109) Module lxml.etree, line 706, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:106817) Module lxml.etree, line 635, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:105671) XMLSyntaxError: PCDATA invalid Char value 20, line 228761, column 21 (line 228761) This is because XML does not accept the full range of characters, there are a few characters that are not allowed. To prevent these errors, we replace these invalid characters by an error character (�) before manipulating the XML with lxml.
-
- 17 Jul, 2020 6 commits
-
-
Xiaowu Zhang authored
See merge request !1193
-
Arnaud Fontaine authored
-
Jérome Perrin authored
We use to have consulting_configurator_sample_categories.ods and standard_category.ods . standard_category.ods was more complete, it contained standard_category.ods that was missing in consulting_configurator_sample_categories.ods . Now standard_category.ods no longer contain "standard" categories, these categories are now installed by business template, so update consulting_configurator_sample_categories.ods to the content of standard_category.ods with all categories (ie. before remove them all in 5e0091a6 )
-
Jérome Perrin authored
Use same spreadsheet for all consulting configurator tests
-
Jérome Perrin authored
When there's only one quantity unit in the group a conversion group, one definition is needed (this might be a bug).
-
Jérome Perrin authored
Instead of using a spreadsheet for categories, use erp5_configurator_standard_categories business template. This business template also configures quantity unit definition in the new way and no longer use obsolete way of setting quantity property on quantity unit categories. The included spreadsheet is still used, but all categories except group and site have been removed, it now only contain group/my_group and site/main.
-