Title: Encoding problem with attribute:description Last modified: September 1, 2016 --- # Encoding problem with attribute:description * Resolved [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/) * I get the error Encoding problem with attribute:description on a few of my products, these look to have html encoded characters like & ' so is there any way I can stop this from happening for the description? I have scoured the source code but can’t see where this might be happening. * Thanks, * Dave * [https://wordpress.org/plugins/wp-product-feed-manager/](https://wordpress.org/plugins/wp-product-feed-manager/) Viewing 12 replies - 1 through 12 (of 12 total) * Thread Starter [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678165) * The examples should be * & amp; & apos; * But with no spaces * Plugin Contributor [wpmarketingrobot](https://wordpress.org/support/users/wpmarketingrobot/) * (@wpmarketingrobot) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678233) * Hello Dave, thanks for contacting us. Could you send us the link to the feed? * Besides that let us know what version of the plugin you are using. * Thanks, Auke. * Thread Starter [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678239) * Hi Auke, thanks for the quick reply! * Here’s the link: [https://www.oxtradtoolsltd.co.uk/wp-content/uploads/wppfm-feeds/Google.xml](https://www.oxtradtoolsltd.co.uk/wp-content/uploads/wppfm-feeds/Google.xml) * The version is 1.1.0 * An example product that merchant center is reporting as being encoded incorrectly is: HY7000LEk * Many thanks, * Dave * Plugin Contributor [wpmarketingrobot](https://wordpress.org/support/users/wpmarketingrobot/) * (@wpmarketingrobot) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678277) * Hi Dave, * We think we found the issue. You encode & signs in your product descriptions and we also encode product text so that causes an issue. Our lead developer is looking at the issue and what to do. * Thanks for the heads-up. * The quick fix would be to not decode & and other signs in your product text. We will also look at the issue. * I report back at you * Auke * Plugin Contributor [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * (@michel-jongbloed) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678300) * Hi Dave, * Could you please upload the following file: * [https://dl.dropboxusercontent.com/u/3129817/class-feed-master.php](https://dl.dropboxusercontent.com/u/3129817/class-feed-master.php) * and then past it in your “wp-content/plugins/wp-product-feed-manager/includes/ application” folder (old file can be overwritten). * Please let us know if that solved the issue. * Thread Starter [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678325) * Hi Michael, thanks for the quick response and sending the fix. * I’ve overwritten the file and re-created the feed but it didn’t fix it unfortunately. * Many thanks, * Dave * Plugin Contributor [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * (@michel-jongbloed) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678329) * Dave, * As far as I can see in your feed (from the link in your reply) the issue seems to be fixed. In the previous version you got & that is now fixed to only & which is correct. Eg. the HY7000LEk product feed looks ok to me now. * Did you reset the feed view? Sometimes you’re still looking at a cached view so resetting the form (F5) could maybe help with that. * But I now see a different (related) issue in the   character. This now shows as   in stead of  . * I will have a look at this asap. And if you disagree with my point that the first issue is fixed, just let me know. * Thread Starter [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678332) * Thanks Michael, yes it looks like it fixed the original issue but as you said this other one has occurred. I ran it through Google merchant center and it looked as if it was the same amount failed but upon checking again, it’s less so the first fix did fix a few! * Thanks again, * Dave * Plugin Contributor [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * (@michel-jongbloed) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678333) * Ok, I updated the file. Please download it again from [https://dl.dropboxusercontent.com/u/3129817/class-feed-master.php](https://dl.dropboxusercontent.com/u/3129817/class-feed-master.php) and place it in the same folder. * Than try it again and let me know if this fixed it. * Thread Starter [viveramedia](https://wordpress.org/support/users/viveramedia/) * (@viveramedia) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678354) * Hi Michel, * I’m still having the same error, I can see & apos; (without space) in product HY7000LEk but that appears to be the only one. * Thanks, * Dave * Plugin Contributor [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * (@michel-jongbloed) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678355) * Hi Dave, * There are 41 occurrences of & apos; in your feed and as far as I know they are fully legal for google. They are so called html special characters and I deliberately use them to replace the appostrof sign (and & amp; for the ampersant and & lt for lesser then eg), because this is best practise for xml feeds. * See [http://www.w3schools.com/html/html_entities.asp](http://www.w3schools.com/html/html_entities.asp) for more information about html special entities. * Did you ran the feed through Google merchant center? Please try that and let me know if they excepted the feed or not. * Plugin Contributor [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * (@michel-jongbloed) * [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678436) * Dave, * We assume the xml feeds are now acceptable for Google feed and thus I will mark this topic as resolved. * But if you’re still encountering issues, please do not hesitate to open this topic again. Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘Encoding problem with attribute:description’ is closed to new replies. * ![](https://ps.w.org/wp-product-feed-manager/assets/icon-256x256.png?rev=3208464) * [WPMR Google Feed Manager for WooCommerce – Sell on Google Merchant Center & Shopping](https://wordpress.org/plugins/wp-product-feed-manager/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-product-feed-manager/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-product-feed-manager/) * [Active Topics](https://wordpress.org/support/plugin/wp-product-feed-manager/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-product-feed-manager/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-product-feed-manager/reviews/) * 12 replies * 3 participants * Last reply from: [Michel Jongbloed](https://wordpress.org/support/users/michel-jongbloed/) * Last activity: [9 years, 9 months ago](https://wordpress.org/support/topic/encoding-problem-with-attributedescription/#post-7678436) * Status: resolved