An error occurred fetching the project authors.
- 04 Nov, 2022 1 commit
-
-
Vincent Pelletier authored
This reverts commit 035d099a. Installing BTs which do not come from produt/ERP5/bootstrap breaks site creation, except in unit tests. This commit is very desirable, but not ready, so unfortunately I have to revert it.
-
- 05 Oct, 2022 1 commit
-
-
Vincent Pelletier authored
So every new instance is able to use self-contained oauh2 authentication. In turn, this triggers atomated migration of a few portal types, which cause the coding style tests to fail. So commit these as well.
-
- 20 Jan, 2015 1 commit
-
-
Gabriel Monnerat authored
erp5_upgrader: Use erp5_full_text_myisam_catalog instead of erp5_full_text_mroonga_catalog because erp5_full_text_mroonga_catalog will be the default
-
- 17 Nov, 2014 1 commit
-
-
Tristan Cavelier authored
- Rename some upgrader scripts - Add upgrader script to check for table existence - Rename some upgrade constraints - Add upgrade constraint (table existence) - Clean up some files
-
- 08 Nov, 2014 1 commit
-
-
Kazuhiko Shiozaki authored
* to quickly setup catalog_full_text table, you can use the following SQL. REPLACE INTO catalog_full_text SELECT uid, title, description FROM catalog; * non fulltext queries like '=abc', '>abc', '%abc%' are supported. * now erp5_full_text_mroonga_catalog is used for unit tests thus I recommend using it instead of erp5_full_text_myisam_catalog. * to migrate existing MyISAM full_text table into Mroonga, you can use the following SQL. ALTER TABLE full_text DROP KEY SearchableText, ENGINE = mroonga, ADD FULLTEXT KEY SearchableText (`SearchableText`) COMMENT 'parser "TokenBigramSplitSymbolAlpha"'; * fulltext search score is no longer provided as (column_name) but now provided as (column_name)__score__. * (category)_title, like source_title, related keys are automatically generated. (category)_description keys as well.
-
- 17 Mar, 2014 1 commit
-
-
Gabriel Monnerat authored
Simplify erp5_upgrader to be possible upgrade any project just enabling the alarms that all Constraints will be called and fixed. The alarms were renamed to cover each step of upgrader and give the possibility to call each step manually one-by-one. Also, all Scripts that the logic can be done by installing Business Template was removed. Also added: - Constraints that can be used in the upgrader - Unit test to check different scenarios - Extend external method to be possible dump workflow chains to be compared with all configuration defined on Business Templates
-
- 10 Sep, 2013 1 commit
-
-
Arnaud Fontaine authored
ZODB Components: Revert 'Allow to execute runUnitTest for bt5 Test Components' (a771dca4) to fix tests bootstrap. The new syntax to load ZODB Tests Components is: runUnitTest BT_TITLE:TEST_NAME That commit was too adhoc as it was relying upon filesystem to load Tests Components and was not behaving like any other Components (versions was not available and other Components were not importable). At the end, it would have meant that a Test Component ran through runUnitTest and Live Tests (in ERP5 itself) would have behaved differently, thus instead: 1/ Install BT_TITLE dependencies and its test dependencies (new bt property to specify bt to be installed only for tests on a fresh instance). 2/ The site is loaded. 3/ Load the test by importing it like any other Components.
-