Title: facing character encoding issue
Last modified: October 9, 2019

---

# facing character encoding issue

 *  Resolved [vinndev](https://wordpress.org/support/users/vinndev/)
 * (@vinndev)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/facing-character-encoding-issue/)
 * I am using the plugin with latest version of wordpress and php7.2
 * i have recently changed DB engine to MyISAM to Innodb after that i am getting
   this error.
 * �;�pwN#r9��WRD�;DMDF ;˦�?J�,]H�h_�-`�5IGr�ұ}�0���]F�[X9�^�S௙NBǧa�V4��x\��݉�L�
   ���`��~��˧O����3�����w�܈��+m�4�/J��S3��mOL�E�ȹ���O�,�\������z�Hw���DJ����ij_w
   �L�cY��%u�Q�����me�����^xuF�O�QF|:����>�H�5#B�p������h�H$��=��;���g���|O`���
   6��ag�-�&I��~��mю�n�[�Q� ����Xÿ��jG�C1zu@��O#�B��@#�^������Ya�e�^+�O)�m�"/�rfu
   ��ϳV�� ��F"�)7ی��I+(S������N�Qt�-hRO��k�o�̜�ʙ�gg�I { �*g���F�?�̚�� Q����#,��*͙
   ���b�h�a-�q�ԧ3��^�&�EhS�灉D%��MU���岓 ��/Q+r���� �? G��'��2����$�΁��<�|kP����
   mY<"U�����i4��� x�}��"~m���կݼB��a�t֨)#�܊l4B;�=%��&ΕY�; &۩���{�ֱ�r���Wn������
   �d�ўR*��1�ˌfe=T�qbb���L�S�x�?A�X��{8�N���#�&`WQ[�i*�7�J�̸�N*���+q�Do�C�9��07Qȃ
   ��dK�7���_�2uCsջb��ޖt#���連���Ug�J�%1eY�>�iz�QYF��ƒۖ̇�Rj��L8;;>�LXD^�9�Ɏt5��Jb
   �� �&�.I�3P�b��F�0n�Hi?�B6����&F� ����~’6�u��eJ��mD� MR��:FU�!�dC~XJ+MJ�M�i Rܹx
   ��ɫ�������p�|+���
 * getting error only with this plugin remaining plugins are working fine.
 * help me out with this issue.
 * Thanks

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [vinndev](https://wordpress.org/support/users/vinndev/)
 * (@vinndev)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/facing-character-encoding-issue/#post-12019242)
 * Is there anyone for help ?
 *  Plugin Author [codisto](https://wordpress.org/support/users/codisto/)
 * (@codisto)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/facing-character-encoding-issue/#post-12019336)
 * Hi,
 * Apologies for the delay. Our frontline support is actually via [support@codisto.com](https://wordpress.org/support/topic/facing-character-encoding-issue/support@codisto.com?output_format=md),
   which is available 24/7 and usually responds within the hour.
 * The issue you are seeing is a result of a content encoding issue. Please see 
   the following help articles for information:
 * [https://get.codisto.help/hc/en-us/articles/235037028-Content-encoding-WooCommerce](https://get.codisto.help/hc/en-us/articles/235037028-Content-encoding-WooCommerce)
 * and the Compression Settings section of:
 * [https://get.codisto.help/hc/en-us/articles/115015413007-Verifying-Troubleshooting-Woocommerce-configuration-for-Codisto-LINQ](https://get.codisto.help/hc/en-us/articles/115015413007-Verifying-Troubleshooting-Woocommerce-configuration-for-Codisto-LINQ)
 *  Thread Starter [vinndev](https://wordpress.org/support/users/vinndev/)
 * (@vinndev)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/facing-character-encoding-issue/#post-12020201)
 * My issue got fixed thank you for the assistance
 * in php.ini zlib.output_compression was off in master but enabled in local.
 * as soon as i disabled in local as well it worked.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘facing character encoding issue’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/codistoconnect_dfeef2.svg)
 * [Omnichannel for WooCommerce: Google, Amazon, eBay & Walmart Integration - Powered by Codisto](https://wordpress.org/plugins/codistoconnect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/codistoconnect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/codistoconnect/)
 * [Active Topics](https://wordpress.org/support/plugin/codistoconnect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/codistoconnect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/codistoconnect/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [vinndev](https://wordpress.org/support/users/vinndev/)
 * Last activity: [6 years, 8 months ago](https://wordpress.org/support/topic/facing-character-encoding-issue/#post-12020201)
 * Status: resolved