Question Gedcom import error

I finally made it to change the php.ini (running WAMP) , now i have this gedcom import error:

SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xF0\x9F\x8C\x9E\x0D1...' for column 'chunk_data' at row 1 (SQL: insert into `mj_gedcom_chunk` (`gedcom_id`, `chunk_data`) values (3, 0 @84599714@ OBJ

Can anyone help me (in easy language) what to do next?

You're importing a GEDCOM file. That is a text representation of all the individuals, families, notes, sources, repositories and other media objects.

It looks like the error is at the media object (usually a photo) identified with @84599714@.

What seems to be wrong here is that it tries to write some binary data (F0 9F 8C 9E 0D1 etc) into a database column that's supposed to hold just text strings. A GEDCOM file is supposed to be just text, and here that seems not to be the case. I'd note that the error message is cut off just where it got interesting. The pattern of \xFF (two hexadecimal characters) is quite odd there: \xFFF (three hexadecimal characters)

May I ask where your GEDCOM file comes from? Is it in an experimental form like the v7 specifications? Usually pictures etc are not transferred within the GEDCOM files themselves. They hold just a reference to them by naming the picture files.

So if the GEDCOM export was done with a feature like "inline media", then try switching that off. You need to transfer the pictures by other means to your data/media folder.

Thank you for responding so quickly. The message was cut off already. I try to find the part in the gedcom with the @84599714@ file. If I can see to what person or family it belongs to I will just delete the picture/media. The file is made in MacFamilytree which has a funny way of making gedcoms, even though the version I export is v.5.5.1.

This is a 4 byte UTF8 character. See recent topic for more info.

If I am correct with your issue, there is a character in your GEDCOM file (an emoji or in my case, a Chinese given name ie a 4 byte UTF8 character) which crashes the database. I found the character by runing the GEDCOM file through Gedcom Validator chronoplexsoftware.com/gedcomvalidator/ and the error will light up as an illegal character. I then replace the character with a question mark, and leave a research task to change it when Greg has the tools to allow us to update the database. I hope that helps.