Using the Advanced Custom Fields plugin, my custom fields have disappeared from ‘New posts’ in the ‘Admin’ back-end.
The fields are also is not listed under screen options either.
Using the Advanced Custom Fields plugin, my custom fields have disappeared from ‘New posts’ in the ‘Admin’ back-end.
The fields are also is not listed under screen options either.
You must be logged in to post a comment.
changes to WP-admin or possibly upgrading WP admin. Were you using the standard custom fields or a 3rd party plugin? It could also be something from a new theme you have installed? Need a little more detail as to what has changed between the last time it worked correctly and now to answer more concisely.
I had a client ask this recently after upgrading WP and it turned out to be very simple check that ‘Custom Field Template’ is checked on the ‘screen options’ drop down menu in the top right of wp-admin.
I’m running into this very problem with the ACF plugin. On my custom posts, the option to show/hide ACF fields (in screen options) is no longer available and the ACF fields are not visible either.
After doing the usual trouble-shooting:
and discovering nothing, I put my site back together. Then I thought, “I wonder if anything ACF related shows up in the page source HTML?”. Sure enough, there was a show/hide ACF checkbox in Screen Options. But it was hidden. This is what Firebug shows:
which has this style:
I have not found a permanent solution yet. But, in FireFox, using Firebug I can disable the
display:none
and set the ACF visibility as I please while I’m creating/editing a custom post. It’s not optimal since the setting doesn’t stick. But it’s a decent work around.Having the same problem as dnagirl above with ACF, but I found a temporary solution to this issue (better than using Firebug):
On your web server, open up plugins>advanced-custom-fields>css>input.css. Or in WP go to Plugins and then Edit the Advanced Custom Fields plugin, then click on “advanced-custom-fields/css/input.css” in the right column. Add the following CSS (doesn’t matter where):
Has anyone found a more permanent solution or cause? This fix I posted will probably stop working whenever the plugin is updated, and would have to be done over again.