Title: Missing post fields
Last modified: October 16, 2018

---

# Missing post fields

 *  [starboard](https://wordpress.org/support/users/starboard1/)
 * (@starboard1)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/missing-post-fields/)
 * I recently updated the plugin on my clients site, and I have a Post Field called‘
   Productions’ which had single line fields ‘year’ ‘duration’ etc.
 * When I updated, the Productions field group was still there, but the single line
   fields have disappeared. They still appear on the actual site, but I can’t edit
   them in WP anymore.
 * I tried adding them back in with Types but it’s saying the field name is already
   in use.
 * Anyone got any suggestions?

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

 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10787438)
 * This is unexpected.
    Can I ask, from what version to what version you updated,
   and if you have a backup of the working site? If such backup exists, I would 
   suggest to deploy it locally and confirm it works as expected on the outdated
   version.
 * Then, enable your working space to debug the website (for example, enable WP 
   [Debug in the install](https://codex.wordpress.org/WP_DEBUG), to log errors)
   
   Check that all is running smooth and is not showing errors. If there are no errors,
   and all is running smooth, make sure to update WordPress in case it’s outdated,
   then Types to it’s the latest version by applying the file downloaded from [here](https://wordpress.org/plugins/types/).
 * Don’t update thru the installer or plugin > update area.
    Update manually in 
   the Local server. If now the same issue happens, start over again and this time,
   exclude other software, like plugins or theme (use Twenty Seventeen) and update
   again manually.
 * At this point, you would remain with the same testing site I have locally, where
   I see no such issues (I usually update existing test sites and re-use them at
   times like these to check).
    However it might also be that the issue by then 
   still happens, then it could be something I miss in my tests, or some other particular
   issue, Server, anything that is “unlike” any other install where this did or 
   does not happen.
 * In that case I usually need to deploy such sites locally myself using a copy 
   of it (Duplicator), but this is a bit difficult here in WordPress ORG forum, 
   where I have no methods to let you provide me such data privately and securely,
   moreover I believe it is not allowed generally, I am not sure, to share such 
   data here in this forum.
 * To note is that Types, as used here, will be [removed by the end of this year](https://toolset.com/2017/11/types-plugin-is-moving-to-be-a-part-of-the-complete-toolset-package/).
   
   Until then we do support it here and also try to solve issues if found (in the
   code).
 * Can you check what happens with the above steps?
 *  [barna](https://wordpress.org/support/users/barna/)
 * (@barna)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10874632)
 * Similar problem here.
 * Previously, I created custom post type with custom taxonomies, and post fields.
   I see the posts with full of data, but I can not modify them. If I change the
   content, I can see it on admin, but not on frontend.
 * If I add new post, and I fill the custom post fields, the post is created, but
   the custom fields are empty. The same issue, I see the posts’ data on admin, 
   but frontend is empty.
 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10874654)
 * [@barna](https://wordpress.org/support/users/barna/) do you have any more steps
   than those, which do not lead to the issue locally?
    Also, please acknowledge
   that Types is about to be deprecated ([https://toolset.com/2017/11/types-plugin-is-moving-to-be-a-part-of-the-complete-toolset-package/](https://toolset.com/2017/11/types-plugin-is-moving-to-be-a-part-of-the-complete-toolset-package/)).
   After 2018 no support or bug fixes are shipped.
 * It might be worth to look out for other solutions if we cannot fix this here 
   and now, however, I’ll try as hard I can to replicate it as well if you have 
   more steps it would help me.
    Also, check the error logs and let me know what
   you see, or/and try with no other plugins, to see if it’s a compatibility issue.
 *  [barna](https://wordpress.org/support/users/barna/)
 * (@barna)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10874822)
 * @bedas Thanks your answer. I tried to use old versions of Types plugin, and I
   changed php version on server, but I couldn’t catch it yet.
    The error log is
   empty. I guess, some kind of plugin conflict cause this. I check this too.
    -  This reply was modified 7 years, 6 months ago by [barna](https://wordpress.org/support/users/barna/).
 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10886466)
 * Did you have any success with?
 * Please let me know

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

The topic ‘Missing post fields’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/types_ced1d3.svg)
 * [Toolset Types - Custom Post Types, Custom Fields and Taxonomies](https://wordpress.org/plugins/types/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/types/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/types/)
 * [Active Topics](https://wordpress.org/support/plugin/types/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/types/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/types/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: Anonymous User 14808221
 * Last activity: [7 years, 6 months ago](https://wordpress.org/support/topic/missing-post-fields/#post-10886466)
 * Status: not resolved