[Resolved] “custom fields” not appearing on edit-custom-post page for new post-type

[Author]

Posts

[Raymond Potter]

I am trying to: Add a new custom post using a post-type and a field group I created previously.

Link to a page where the issue can be seen: Back end issue, so not visible.

I expected to see: My set of custom field available to select in the edit page

Instead, I got: all the regular data entries, but no access or drop-down for the custom field group attached to the custom post type.

I further tried to duplicate a working post type as another new post type, and change the field group usage, but that did not work either.

Existing custom post types that I tested seem to display correctly. I tried to compare them to the problem post, but could not find an apparant difference.

Please advise.

[Nigel]

Hi Raymond

I've seen another couple of reports of problems displaying custom field groups on the post edit screen but we haven't found a common thread or been able to reproduce yet, let's see what we can find in your case.

First, do you see any warnings or errors in your PHP logs?

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

That will create a debug.log file in your /wp-content directory which you can examine in any text editor.

Re-visit the problem post edit screen and then inspect the log.

Next, can you also do a conflict test?

Change theme to twentyseventeen and test again with the problem post type.

Also, disable all non-Toolset plugins and re-test.

Does anything change?

[Raymond Potter]

I will work on these steps. Where do I find the PHP logs?
Thanks.

[Raymond Potter]

"...Change theme to twentyseventeen and test again with the problem post type..."

Done. All Custom PT show their Custom Field Groups except the one in question. No Effect

Resetting theme back to Make now.

[Raymond Potter]

I set up the debug logs and browsed the site. A plugin called "SEO friendly images" was kicking up a lot of deprecated syntax errors.

I cleared the log, and I disabled the specific plugin. No more errors appeared in the log. I will leave the plugin, which was last updated 3 years ago, offline.

I cleared the log. To make sure the logger was working, I added a dummy line to the end of a plugin php, which I knew worked. It crashed the plugin and the logger recorded this. I fixed the php and everything worked fine on that page.

In between, I visited the new post page for the post type in question. My custom field set did not appear and the logger detected nothing.

🙁

[Nigel]

Hi Raymond

Thanks for those details, I think I will need a copy of your site to test locally and possibly pass on to my colleagues for further debugging if needed.

Could I get you to provide a duplicate? hidden link

I've marked your next reply as private.

[Nigel]

Hi Raymond

I can't access the archive, you need to give me permission (you can use nigel.a@onthegosystems.com).

[Raymond Potter]

try now. I sent you a share link to that email addy.

[Nigel]

Hi Raymond

I installed the copy of your site, did quite a bit of testing, confirmed the issue.

I was preparing a slimmed-down version of the site to pass on to my colleagues with only the Types plugin and twentyseventeen theme and I updated Types to 3.0.2, which was released just a few hours ago.

One last check to confirm the issue persisted—but it was gone.

Updating to Types 3.0.2 appears to have solved the problem.

Could you update your own site and confirm?

[Raymond Potter]

I will try to confirm, but the plugin directory, even after refresh is not showing an update from 3.0.01 yet

Also, I assume I can delete the zipped site file now?

[Nigel]

You should see an option to update Types to 3.0.2, but if not you can always download it from toolset.com/account/downloads and update it manually.

Yes, you can delete the linked duplicate of your site now, thanks.

[Raymond Potter]

It works! Thanks so much. I hope you will fix this (apparent) bug for all your customers!