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.
-
- 05 Sep, 2020 1 commit
-
-
Arnaud Fontaine authored
-
- 07 Mar, 2016 1 commit
-
-
Georgios Dagkakis authored
All business templates migrated to new format with files like Python Scripts, Web Pages, Web Scripts etc. separate to xml
-
- 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.
-
- 04 Jan, 2014 1 commit
-
-
Sebastien Robin authored
-