Apostrophe in Views front-end filters fields is being escaped with a backslash

Symptoms

There is an issue where apostrophes in custom fields names or options are escaped when fields are used on the front-end for custom search filtering.

The issue happens when one of the following is used for filtering the custom search on the front-end:

• A custom field created using Types that has an apostrophe in the field name.
• A Checkbox, Multiple checkboxes or Radio custom field created using Types, where the field has an apostrophe in then name of any options.

On the front-end, the apostrophe in the name of the field or in the name of the option is escaped with a backslash.

Workaround

There is no workaround for this issue.

The development team is aware of the issue and will work on it as soon as possible.