Sabina Talipova
c1eaaaabfa
MNT Remove TODO comments
2023-10-19 16:22:38 +13:00
Steve Boyd
30685c9227
MNT Remove legacy upgrader config
2023-01-20 17:13:11 +13:00
Guy Sartorelli
911a71d6f6
Merge branch '4' into '5'
2022-11-21 18:07:57 +13:00
Guy Sartorelli
f2c4423d0c
Merge branch '4' into 5
2022-08-31 13:56:26 +12:00
Mike Cochrane
2219899c10
MNT Use SiteTree instead of Page in tests
2022-08-25 10:17:41 +12:00
Robbie Averill
79f3fd723d
FIX Use publishRecursive() over doPublish()
...
doPublish() is deprecated.
2022-08-24 16:08:45 +12:00
Steve Boyd
1b0b2154b4
ENH PHP 8.1 compatibility
2022-04-13 17:07:59 +12:00
Steve Boyd
360fbcd878
API phpunit9 support
2021-10-28 10:40:52 +13:00
Steve Boyd
e98110d336
MNT Update tests to use logInAs() ( #2679 )
2021-08-18 12:35:36 +12:00
Garion Herman
8a16d708d4
FIX Use Live stage to fetch results during SearchFormTest
...
This resolves an issue with the testUnpublishedPagesNotIncluded case
when running against PostgreSQL.
2020-10-22 14:42:27 +13:00
Michal Kleiner
d8331c1e0a
Use short array syntax across the module's codebase
2020-04-19 16:18:01 +12:00
Ingo Schommer
e51bd421a6
FIX InnoDB FULLTEXT compat in tests
...
> InnoDB FULLTEXT indexes have special transaction handling characteristics due its caching and batch processing behavior. Specifically, updates and insertions on a FULLTEXT index are processed at transaction commit time, which means that a FULLTEXT search can only see committed data. The following example demonstrates this behavior. The FULLTEXT search only returns a result after the inserted lines are committed.
https://dev.mysql.com/doc/refman/5.6/en/innodb-fulltext-index.html#innodb-fulltext-index-transaction
2020-04-09 11:05:19 +12:00
Ingo Schommer
dd839ca2d9
FIX Remove searchEngine() test that's using API wrong
...
Required to allow InnoDB usage, see https://github.com/silverstripe/silverstripe-framework/pull/9454 .
This came up in https://github.com/silverstripe/silverstripe-cms/issues/1452 , and wasn't fully addressed.
Either we allow boolean mode and all the constraints this brings around special character usage,
or we filter out those special characters, which makes boolean mode pointless.
You can't just pass arbitrary user input in a power-user function like this.
See https://dev.mysql.com/doc/refman/5.6/en/fulltext-boolean.html
Context: This used to work for some examples like "foo>*" under MyISAM,
presumably because it had a more lenient parser. InnoDB rightfully complains about this now.
2020-04-09 09:59:53 +12:00
Sam Minnee
5e3068ba13
MINOR: Add tests for some search-form fixes
...
These 2 tests validate that the following bugs have been fixed.
https://github.com/silverstripe/silverstripe-framework/issues/3212
https://github.com/silverstripe/silverstripe-cms/issues/1452
2018-11-10 12:07:49 +13:00
Luke Edwards
2fbeda1564
ADD New search component for SiteTree ( #2224 )
2018-09-04 13:13:33 +12:00
Raissa North
6b2a9e4f77
Update class references and array syntax
2018-06-20 13:18:29 +12:00
Damian Mooyman
8c6c429994
Update API to remove deprecated useDraftSite()
...
Update to support versioned enhancements
2018-03-22 17:12:12 +13:00
Damian Mooyman
4f6af36369
Manual fixes to automatic namespacing
2017-08-09 17:09:28 +12:00
Damian Mooyman
9f268a18b5
Run add-namespace command
2017-08-09 17:00:58 +12:00
Damian Mooyman
6cb2077878
Move files to new location
2017-08-09 16:58:07 +12:00
