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
If you're filing a bug, please describe how to reproduce it. Include as much
relevant information as possible, such as:
Bug summary
We are using query_search to filter a certain listing page, where the query looks like contenttype?anyField--like=query.
This works fine, as long athe query does not contain german umlaute, a "sharps" (ß) or certain special characters like /.
I'm fairly certain, this issue is caused by the encoded values stored in bolt_field_translation. A value containing / would look like ["u-7954\/26"]. For umlaute f\u00fcr is stored instead of für. Changing this values manually in the database makes the records appear in the filter results.
Steps to reproduce
Create a content type with a simple text field.
Crate a record containing umlaute or slashes.
Search for the record in frontend
Expected result
The record should show um in the results.
Actual result
It does not.
The text was updated successfully, but these errors were encountered:
Details
Reproduction
If you're filing a bug, please describe how to reproduce it. Include as much
relevant information as possible, such as:
Bug summary
We are using
query_search
to filter a certain listing page, where the query looks likecontenttype?anyField--like=query
.This works fine, as long athe query does not contain german umlaute, a "sharps" (
ß
) or certain special characters like/
.I'm fairly certain, this issue is caused by the encoded values stored in
bolt_field_translation
. A value containing/
would look like["u-7954\/26"]
. For umlautef\u00fcr
is stored instead offür
. Changing this values manually in the database makes the records appear in the filter results.Steps to reproduce
Expected result
The record should show um in the results.
Actual result
It does not.
The text was updated successfully, but these errors were encountered: