- 31 Aug, 2020 1 commit
-
-
Jérome Perrin authored
Person.setUserId is heavy, it serializes person module to prevent concurrency, but in some cases we the risk of having duplicate user ids is under control, so we don't want to pay the performance price. See merge request !1242
-
- 27 Aug, 2020 1 commit
-
-
Arnaud Fontaine authored
-
- 26 Aug, 2020 1 commit
-
-
Gabriel Monnerat authored
-
- 25 Aug, 2020 3 commits
-
-
Xiaowu Zhang authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
- 24 Aug, 2020 4 commits
-
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
- 21 Aug, 2020 5 commits
-
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
- 19 Aug, 2020 8 commits
-
-
Xiaowu Zhang authored
See merge request nexedi/erp5!1243
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
padding too much in buttom make header bigger, so when export to pdf, header is cut off to hit heigth which make logo display at top
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored
-
- 18 Aug, 2020 2 commits
-
-
Xiaowu Zhang authored
-
Jérome Perrin authored
also needs to be declared in hidden content types to prevent adding directly in preferences
-
- 17 Aug, 2020 6 commits
-
-
Jérome Perrin authored
This activity is spawned on all nodes, which cause too many conflicts. We can take the risk here, assuming that references were already OK before migration.
-
Jérome Perrin authored
Person.setUserId does expensive checks to ensure that user ids are uniques, but the default id generator already guarantees unicity, so when default id generator is used we don't need Person.setUserId unicity checks. Now when generating user ids, we only consider user id conflict with existing users, because it's not so expensive and might still happen, for example if user ids have been migrated from person references when erp5_users PAS plugin was used. person.setUserId still performs the expensive checks to prevent duplications against other transactions using person.setUserId, but not against other transactions using person.initUserId
-
Jérome Perrin authored
should be same for cases where type based method is a python script, but is a bit more explicit/safe and consistent with other usages.
-
Jérome Perrin authored
In 93e30e5e (Person: Store user id in new user_id property., 2016-12-09) we adapted this test to the new behavior: title fallback to user_id or id, but since persons always have a user_id by default, this test was changed to check that title fallbacks to user_id, but the name of the test still mention "fallback to id" which became a bit different from what was tested here. Revert testEmptyTitleFallbackOnId to check that title fallbacks on id, using persons without user id and introduce new testEmptyTitleFallbackOnUserId to describe the new behaviour with user id.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 14 Aug, 2020 4 commits
-
-
Rafael Monnerat authored
See merge request nexedi/erp5!1244
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
- 13 Aug, 2020 1 commit
-
-
Xiaowu Zhang authored
See merge request nexedi/erp5!1241
-
- 12 Aug, 2020 4 commits
-
-
Roque authored
-
Xiaowu Zhang authored
-
Xiaowu Zhang authored