You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Normally, this does not need to be touched, as this package supports all Neos data types natively.**
532
+
**The default configuration supports most usecases and often may not need to be touched, as this package comes with sane defaults for all Neos data types**
533
533
534
534
Indexing of properties is configured at two places. The defaults per-data-type are configured
535
535
inside `TYPO3.TYPO3CR.Search.defaultConfigurationPerType` of `Settings.yaml`.
If your nodetypes schema defines custom properties of type DateTime, you have got to provide similar configuration for them as well in your NodeTypes.yaml, or else they will not be indexed correctly.
579
+
578
580
There are a few indexing helpers inside the `Indexing` namespace which are usable inside the
579
581
`indexing` expression. In most cases, you don't need to touch this, but they were needed to build up
580
582
the standard indexing configuration:
@@ -647,6 +649,12 @@ currently configured in PHP, the configuration for any property in a node which
647
649
This is important so that Date- and Time-based searches work as expected, both when using formatted DateTime strings and
648
650
when using relative DateTime calculations (eg.: `now`, `now+1d`).
649
651
652
+
If you want to filter items by date, e.g. to show items with date later than today, you can create a query like this:
0 commit comments