Title: Error with Version 1.0.4
Last modified: August 22, 2016

---

# Error with Version 1.0.4

 *  Resolved [Kelly3k9](https://wordpress.org/support/users/kelly3k9/)
 * (@kelly3k9)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/)
 * Hi,
 * I had the problem with my existing custom taxonomies disappearing when I installed
   the last update – just dropping by to say the same is happening with 1.0.4 too.
   I’ve gone back to 0.9.5 for now, which works a charm.
 * Thanks!
 * [https://wordpress.org/plugins/custom-post-type-ui/](https://wordpress.org/plugins/custom-post-type-ui/)

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

 *  [Trevsweb](https://wordpress.org/support/users/trevsweb/)
 * (@trevsweb)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877714)
 * Hi Kelly do you have a zip of 0.9.5? I would really like to get mine working 
   again 🙂
 *  Thread Starter [Kelly3k9](https://wordpress.org/support/users/kelly3k9/)
 * (@kelly3k9)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877717)
 * I downloaded mine from here
    [https://downloads.wordpress.org/plugin/custom-post-type-ui.0.9.5.zip](https://downloads.wordpress.org/plugin/custom-post-type-ui.0.9.5.zip)
 * Courtesy of the plugin developer – thank you!
 *  Plugin Contributor [Michael Beckwith](https://wordpress.org/support/users/tw2113/)
 * (@tw2113)
 * The BenchPresser
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877782)
 * From my experience with first-hand helping, just re-associating the post types/
   taxonomies and hitting save has actually fixed the issue. Doesn’t help me figure
   out why it’s a setting that gets lost in the first place, but it solves the issue
   on individual user ends.
 *  [brianchicago76](https://wordpress.org/support/users/brianchicago76/)
 * (@brianchicago76)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877807)
 * Just to confirm Mr. Beckwith’s reply, I just upgraded to 1.0.4 today and none
   of the permalinks for my custom post types were working (“Page not found” error).
   However various data within the posts were still visible in other parts of the
   site (Featured Image, etc.). So I figured it must be some way the CPTs were being
   stored and synced in the db that had to be reinitialized. All you need to do 
   is go under “CPT UI > Add/Edit Post Types > Edit Post Types,” then select each
   existing post type from the drop down and click “Edit Post Type” (but don’t alter
   anything!). As I said I think this just “reinitializes” or “reserializes” the
   CPT data the db after this latest version update. Your posts should start working
   again… at least mine did. Hope this helps.
 *  Plugin Contributor [Michael Beckwith](https://wordpress.org/support/users/tw2113/)
 * (@tw2113)
 * The BenchPresser
 * [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877821)
 * Wish these settings converted more cleanly than they seem to have for a lot of
   people, but good to know that this step still works for some.

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

The topic ‘Error with Version 1.0.4’ is closed to new replies.

 * ![](https://ps.w.org/custom-post-type-ui/assets/icon-256x256.png?rev=2744389)
 * [Custom Post Type UI](https://wordpress.org/plugins/custom-post-type-ui/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/custom-post-type-ui/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/custom-post-type-ui/)
 * [Active Topics](https://wordpress.org/support/plugin/custom-post-type-ui/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/custom-post-type-ui/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/custom-post-type-ui/reviews/)

 * 5 replies
 * 4 participants
 * Last reply from: [Michael Beckwith](https://wordpress.org/support/users/tw2113/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/error-with-version-104/#post-5877821)
 * Status: resolved