Title: WordPress 3.8 compatibility fix
Last modified: August 21, 2016

---

# WordPress 3.8 compatibility fix

 *  [Jared Atchison](https://wordpress.org/support/users/jaredatch/)
 * (@jaredatch)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/)
 * It looks as if this plugin is no longer actively developed.
 * However if you are using it, some fine folks have posted a pull request on GitHub
   that fixed things that broke in WordPress 3.8.
 * [https://github.com/mfields/Taxonomy-Images/pull/24](https://github.com/mfields/Taxonomy-Images/pull/24)
 * This is a good fix, however at this point I would recommend using a different
   plugin for future sites.
 * [https://wordpress.org/plugins/taxonomy-images/](https://wordpress.org/plugins/taxonomy-images/)

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

 *  [nowton](https://wordpress.org/support/users/nowton/)
 * (@nowton)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773836)
 * Hi Jared, which alternative are you referring to?
 *  [nowton](https://wordpress.org/support/users/nowton/)
 * (@nowton)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773841)
 * Thanks, merged from Git.
 *  [Travis](https://wordpress.org/support/users/tjtaylor/)
 * (@tjtaylor)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773851)
 * Hi Jared,
 * What different plugin would you recommend?
 * Thanks!
 *  [maorb](https://wordpress.org/support/users/maorb/)
 * (@maorb)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773852)
 * I have this same issue on a site using WP3.8 with this plugin.
    I’ve merged the
   fixes from Git, it did change the UI, but still the image is not actually being
   saved to the field. I’ve checked the js console, but no errors there. Do you 
   have an idea what can fix this?
 * Update: updating to WP3.9 on dev server of this site appears to partially solve
   the issue. It now attaches new images if image is uploaded from computer, but
   won’t attach images that already exist in media library.
 * Thanx
 *  [Dan Knauss](https://wordpress.org/support/users/dpknauss/)
 * (@dpknauss)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773855)
 * I’m not seeing any problems with WP 3.9.x. Is this plugin maintained anymore?
   What’s the future plan with the forked version on GitHub?
 *  [Travis](https://wordpress.org/support/users/tjtaylor/)
 * (@tjtaylor)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773856)
 * Hello,
 * Just wanted to mention that I recently found out that you can use Advanced Custom
   Fields to attach images to taxonomies, categories, tags, etc; along with many
   other custom field options…
 * [https://wordpress.org/plugins/advanced-custom-fields/](https://wordpress.org/plugins/advanced-custom-fields/)
 * On top of that you can use Codepress Admin Columns to add the image to the admin
   column.
 * [https://wordpress.org/plugins/codepress-admin-columns/](https://wordpress.org/plugins/codepress-admin-columns/)
 * Hope this helps someone!

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

The topic ‘WordPress 3.8 compatibility fix’ is closed to new replies.

 * ![](https://ps.w.org/taxonomy-images/assets/icon-256x256.png?rev=1283547)
 * [Taxonomy Images](https://wordpress.org/plugins/taxonomy-images/)
 * [Support Threads](https://wordpress.org/support/plugin/taxonomy-images/)
 * [Active Topics](https://wordpress.org/support/plugin/taxonomy-images/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/taxonomy-images/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/taxonomy-images/reviews/)

 * 6 replies
 * 5 participants
 * Last reply from: [Travis](https://wordpress.org/support/users/tjtaylor/)
 * Last activity: [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-38-compatibility-fix/#post-4773856)
 * Status: not resolved