- 30 Sep, 2019 4 commits
-
-
Roque authored
This reverts merge request !916 Merged by mistake /reviewed-on nexedi/erp5!942
-
Sebastien Robin authored
This reverts commit f9f020e3.
-
Arnaud Fontaine authored
Assuming that the test database already exists and 'movement' table already contains data (from past execution for example), on '--save' before this commit: 1. Create a new ERP5 Site: 1. Install erp5_mysql_innodb_catalog. 2. Call ERP5Site_reindexAll(clear_catalog=True) (from ERP5Generator.setupIndex()). => At this point, erp5_mysql_innodb_catalog tables are recreated. 2. Install erp5_movement_table_catalog or any bt5 adding a new SQL table. => This does not recreate the table and leave the existing data as it is. 3. Dump MySQL database to dump.sql. => dump.sql contains 'INSERT INTO' for 'movement' table *before* this '--save'. This fixes random customer Unit Tests failures on SQL queries accessing 'movement' table directly and getting {non-existing,past executions} Movements.
-
Yusei Tahara authored
-
- 29 Sep, 2019 1 commit
-
-
Roque authored
Fixes, refactoring, details and more app migrations. /reviewed-on nexedi/erp5!916
-
- 27 Sep, 2019 10 commits
-
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Roque authored
-
Xiaowu Zhang authored
This reverts commit b6b517ee. which impacts "Time Table Line" and "Public Holiday Line" portal tyle I need to check more portal type before remerge it
-
Roque authored
-
Sebastien Robin authored
-
Ivan Tyagov authored
-
Jérome Perrin authored
This field was only displayed if any of these was enabled: - by function analytics - by project analytics - by category analytics and it allows requesting reports per function, project, categories and section. The problem is that if any analytics was explicitly enabled, we never allow users to get a break down by section. Always display the field, so that user can always select section. This does not make much sense when there's only one section though. /reviewed-on !939
-
- 26 Sep, 2019 2 commits
-
-
Roque authored
-
Kazuhiko Shiozaki authored
-
- 25 Sep, 2019 10 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Xiaowu Zhang authored
Before this change, class hierarchy is like this when using mixin: ``` class MyClass(BaseClass, Mixin1....) ``` which is usually ok when classes don't override each other's But if we want to overwrite BaseClass's method by using mixin to do more thing, For example: ``` class BaseClass(object): def test(self): print 'base test' class Mixin1(object): def test(self): super(Mixin,self).test() print 'mixin' ``` I want to display 'mixin base test' when call test, but it doesn't work since priority of how methods are resolved is from left to right: BaseClass----->Mixin1, it only display 'base test' So the correct way to use mixin should be in reverse order: ``` class MyClass(Mixin1, BaseClass) ``` /reviewed-on nexedi/erp5!935
-
Roque authored
-
Roque authored
-
Jérome Perrin authored
When other nodes takes time to start they are not always registered when the "main" node asserts that they are there. We observed problems in an environment where resolving localhost (by DNS) takes 10 seconds. Also introduce getOtherZopeNodeList utility method that can be useful in other ZEO tests in ProcessingNodeTestCase
-
Jérome Perrin authored
When other zope nodes takes time to start this sometimes causes conflict.
-
- 24 Sep, 2019 12 commits
-
-
Romain Courteaud authored
Reset mailhost before each test. Commit changes created by portal_transforms.
-
Romain Courteaud authored
-
Romain Courteaud authored
This allows restoring the correct skin selection in ERP5JS. Deferred reports can now be used in ERP5JS. REQUEST is used to support direct form rendering, like: ./Base_viewHistory?deferred_portal_skin=ODS&portal_skin=Deferred Thanks to Georgios Dagkakis for his work on this topic. See !702
-
Roque authored
- corresponding test update
-
Roque authored
- corresponding test update
-
Roque authored
- corresponding tests update
-
Roque authored
-
Roque authored
-
Roque authored
- corresponding test update
-
Roque authored
- corresponding test update
-
Roque authored
- new storage layer on top of appcache storage to manage officejs configuration elemnts - the elements listed in ".configuration" app manifest are got from appcache and stored in current app storage as documents - storage cleaner to handle data migration
-
Roque authored
- reorginize and extend app setting and customization - each portal type has its own setting dictionary - handling blob types in document render and submit - remove hardcoded app configuration manifest - allow custom view in controller - common configurations refactored - handle_action handles notify submit and redirect base on custom action return - controller default page forces storage sync if app version changes - fix 401 login redirect in storage selection - general code refactoring and cleanup
-
- 23 Sep, 2019 1 commit
-
-
Kazuhiko Shiozaki authored
otherwise it loses too much precision.
-