Title: sincityserver's Replies | WordPress.org

---

# sincityserver

  [  ](https://wordpress.org/support/users/sincityserver/)

 *   [Profile](https://wordpress.org/support/users/sincityserver/)
 *   [Topics Started](https://wordpress.org/support/users/sincityserver/topics/)
 *   [Replies Created](https://wordpress.org/support/users/sincityserver/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/sincityserver/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/sincityserver/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/sincityserver/engagements/)
 *   [Favorites](https://wordpress.org/support/users/sincityserver/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Content Encoding Error when Editing Product](https://wordpress.org/support/topic/content-encoding-error-when-editing-product/)
 *  Thread Starter [sincityserver](https://wordpress.org/support/users/sincityserver/)
 * (@sincityserver)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/content-encoding-error-when-editing-product/#post-8926460)
 * The way I fixed the issue was I compared a product that did not produce a content
   encoding error with the product that did. I found that the product causing an
   issue was missing attributes in the post_meta table. I inserted one attribute
   for the product int the table and the problem went away on the front end. I found
   that the products had been inserted using an import tool and somehow some products
   were not given any attributes and such products are still producing content encoding
   errors in wp-admin.

Viewing 1 replies (of 1 total)