Nope, comes straight from the JSON. I put the json file in the
Looks like this:
Mungungo��������������������������������������������������������������������������������������������������������������������� when viewing it in browser
Anyone have an idea why non-ascii characters would be inserted into a JSON file on PHP 7.x but works completely fine on PHP5.x?
Curious, do you ~just~ define that in http://type.ss?
You need to escape it, before you pass the query to Solr right?
You might need to add \ before the apostrophe?
Quick question, how to people handle managing a has-one relationship in a drop-down in the CMS when there's too many options and it fallsback to a NumericField? Just bump up the
dropdown_field_threshold (with too many items, this might exceed the PHP memory when it needs to create too many DOs) or something smarter? Making the CMS user put in the ID of the has-one object isn't ideal for most I'd think? Use the has_one field module maybe?
Try the following settings maybe @Ramon Lapenta?
- connection_charset: utf8mb4
- connection_collation: utf8mb4_unicode_ci
- charset: utf8mb4
- collation: utf8mb4_unicode_ci
The author might be lurking somewhere here
Any particular repo you’re looking at haha?