Feed encoding problem

Looking deeper into the issue, feed unconditionally inserts BOM characters (0xEF 0xBB 0xBF). While it is useful for encodings like UTF-16, but somewhat questionable for UTF-8. There are argument for and against it.

Anyway, I currently modified the plugin code not to insert those and submitted updated feed to Fruugo. Waiting for their reply.

I think, insertion of the BOM should be an option presented in the feed preference where one select feed file format.

Can you share the change you made with us (when Fruugo accepts your feed)?

classes/class-get-products.php

I removed line 2272:

fputs( $fp, $bom = chr(0xEF) . chr(0xBB) . chr(0xBF) );

This functionality should really be optional.

This change allowed Fruugo to accept the file. There are more issues in the feed itself that I fixed (I think I did) by manipulating mapping of the fields, but waiting for them to approve the feed. Once they confirm fix, I will let you know

Ok, thanks. We will look into it.

I think you could have also solved the issue at hand by providing Fruugo with a XML feed instead of a CSV feed?

They asked for CSV, but I should enquire about feed being in XML.

Fruugo is a very strange marketplace — one can not simply submit a feed. It has to be approved by an “integration specialist” first. Originally, Fruugo assigned me one — CED commerce and CSV requirement came from them. CED also told me I can only submit feed through them and there is no other way! After learning that quality of their software was pretty crap, I asked Fruugo if there is another way and Fruugo told me to just submit feed to them directly. This is when I started to use Product Feed Pro, but I never questioned file format.

We have just pushed out version 12.6.2 of our plugin that removes the BOM characters for Fruugo CSV feeds.