Making autoFilter Case-Insensitive in Evolution CMS

If a text filter treats `Home` and `home` as different values, normalize the comparison layer instead of forcing editors to type perfectly.

Case-sensitive filters feel broken to users, especially when the value comes from free text or editorial input. If Home and home produce different results, the filter logic needs normalization.

What usually works

lowercase the incoming filter value before matching
store or compare against normalized lowercase data
avoid mixing multiple spellings of the same label in content

Case-insensitive filtering is not just a convenience feature. It makes the interface feel resilient and reduces editorial inconsistency in the underlying dataset.

Newer post

Using a Central Exchange Rate for Shopkeeper Pricing

How to keep Shopkeeper prices tied to a single exchange-rate value so a whole catalog can react to one update.

Older post

Adjusting TV Field Sizes and the Main Content Area in the Manager

How to think about resizing TV input fields and the main content area when ManagerManager is not enough on its own.