- 08 Dec, 2020 2 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
Work done by Wenjie Zheng, Isabelle Vallet and Sebastien Robin.
-
- 30 Nov, 2020 1 commit
-
-
Arnaud Fontaine authored
-
- 26 Nov, 2020 15 commits
-
-
Roque authored
See merge request nexedi/erp5!1275
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
- this action relies on paged.js library for pagination
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Jérome Perrin authored
Don't log and fix a few resource warnings See merge request nexedi/erp5!1307
-
Nicolas Wavrant authored
Add missing field, used in testFloatFieldStep
-
- 23 Nov, 2020 2 commits
-
-
Nicolas Wavrant authored
It follows commit ce233f79
-
Nicolas Wavrant authored
-
- 17 Nov, 2020 4 commits
-
-
Romain Courteaud authored
Some fields may use div element without expecting 100% width. Example: formbox and diff gadget.
-
Jérome Perrin authored
this prevents ResourceWarnings on python3
-
Jérome Perrin authored
this prevent ResourceWarnings on python3
-
Jérome Perrin authored
this is way to verbose and not really useful
-
- 13 Nov, 2020 2 commits
-
-
Vincent Pelletier authored
Why invent a different way, making it harder to consistently patch validated_hook ?
-
Vincent Pelletier authored
For example, allows upgrading a Business Template when an ERP5 Form is replaced by a PythonScript in a skin folder.
-
- 12 Nov, 2020 1 commit
-
-
Jérome Perrin authored
When running on testnode, runUniTest is responsible for picking a free $DISPLAY. This is implemented by starting Xvfb on a $DISPLAY, waiting a bit and if it is still running we assume the $DISPLAY was free. But it seems sometimes we don't wait enough, when testnodes are overloaded. This implementation is wrong, we could run a command check that X is running, but as explained in the code command below, xdpyinfo or other tools are currently not available in test environment. Since we are considering switching this to seleniumserver (which would take care of running a X Server for us) so this is OK for now.
-
- 11 Nov, 2020 1 commit
-
-
Jérome Perrin authored
there was also another script for internal
-
- 09 Nov, 2020 1 commit
-
-
Jérome Perrin authored
This test was clicking on the first item in a non sorted list and then checking that the text of the selected element was "a2". Instead, store the text of the first listbox cell in a variable and use this in check.
-
- 05 Nov, 2020 2 commits
-
-
Jérome Perrin authored
Implement related keys for translated relations (like `source__translated__title`) and change content translation to index categories, by also indexing types whose translation is set in Localizer. See merge request nexedi/erp5!1292
-
Jérome Perrin authored
Extend stock report dialog to allow choosing a (simple) valuation method ![stock report dialog screenshot](/uploads/2e0fa7c420954c3f84260605b3a6930e/image.png) which be displayed in a new column, showing the inventory value for each line See merge request nexedi/erp5!1203
-
- 04 Nov, 2020 6 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
Changing the language and browsing to another web section require to fully refresh the page.
-
- 29 Oct, 2020 3 commits
-
-
Jérome Perrin authored
Now that we are able to search using content translation, we also want to extend this so that columns like "group__title" can be searchable in listboxs, but categories are usually translated with `erp5_content`, which was not indexed in content_translation table. Extend content translation indexing to also support translations coming from Localizer catalog make this possible. The only limitation I could think of is that categories will need to be reindexed when the messages are modified in catalog.
-
Jérome Perrin authored
Translated properties are indexed in content translation table, so nothing prevent us from using them in related keys. Since in many places we show to user translated titles in relations, it makes sense to also support searching and sorting in catalog. This extends related keys syntax only for the newest syntax, so related keys like `source__translated__title=X` would allow searching for document who have a source relation to a document with title X. Since any properties can be translated, if for example a property `foo` would exist and be translatable, it would be possible to search using `source__translated__foo=X` This is only available when content_translation business template is installed.
-
Nicolas Wavrant authored
The default value of the field was calling Base_getEditorFieldPreferredTextEditor and returned the preferred text editor, because this script assumes the content type to be text/html by default
-