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
2019-11-13 10:21:52 +13:00
2020-02-17 02:29:19 +00:00
2017-10-03 17:05:54 +13:00
2017-10-12 11:30:11 +13:00
2016-05-11 09:46:28 +12:00
2016-09-27 17:10:47 +13:00
2020-02-28 13:49:24 +13:00
2018-04-12 16:06:49 +12:00
2020-02-28 13:49:24 +13:00
2019-11-18 15:30:41 -04:00
2019-11-05 16:50:41 +13:00
2019-12-13 18:40:52 +00:00

SilverStripe CMS

Build Status Latest Stable Version Latest Unstable Version codecov SilverStripe supported module Total Downloads License Dependency Status Reference Status

PHP Content Management System (CMS), see http://silverstripe.org. Requires the framework module and a silverstripe-installer base project.

Installation

See installation instructions.

Bugtracker

Bugs are tracked on github.com. Please read our issue reporting guidelines.

Development and Contribution

If you would like to make changes to the SilverStripe core codebase, we have an extensive guide to contributing code.

Description
No description provided
Readme 28 MiB
Languages
PHP 73.3%
JavaScript 20%
Gherkin 4%
Scheme 2.1%
SCSS 0.6%