Skip Navigation

[Resolved] Post Fields not displaying on post type

This support ticket is created 6 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Beda 6 years, 3 months ago.

Author
Posts
#1108531

I am trying to: Add custom post fields to products

Link to a page where the issue can be seen: Edit product page

I expected to see: Post fields so that I can update more product data

Instead, I got: nothing

#1108761

Usually if you install WooCommerce and Types, then in Toolset > Custom Fields > Post Fields you will already have a Post Field Group for WooCommerce Products that are used by Toolset for specific WooCommerce data handling.

This group is usually called "WooCommerce Views filter fields" and should be left as is, if possible.

To add more field to the WooCommerce Products, you can add new "Custom Fields > Post Fields" and assign that Group to the Product Post Type.
Then start adding Fields to the Group, and they will appeaer in WooCommerce's Products as tested locally.

It may be a conflict with another theme or plugin if this does not work on your end.

I would suggest trying to replicate the issue with just Toolset, WooCommerce and Theme Twenty Seventeen, if the porblem then is solved, please find the culprit plugin/theme by re-enabling each one a time.
Report that plugin/theme to us, we will see what we can do.

If the issue persist after above null-conflict test, could you then add the precise steps to achieve the issue, so we can replicate this and solve it?
It may help to add step by step descriptions of what you do, or screenshots, or a copy of your site with an instruction as of where and how to see the issue.

Remember that first we would check compatibility issues, which can be excluded by above no-conflict test.

We as well will help if the issue is not with our plugin, we will try to contact the author and collaborate on a fix, if any 3rd party is culprit of the issue, or of course, fix the issue in Toolset if we manage to replicate it 🙂