This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here was that the users custom field group was showing up on another Custom Post Type.
Solution:
To resolve this you need to edit your custom field group settings and ensure that only the CPT that you want to be affected is selected.
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.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
This topic contains 5 replies, has 2 voices.
Last updated by 6 years, 2 months ago.
Assisted by: Shane.
Hi Eric,
The issue seems to be caused by this option here. See Screenshot.
Your posts are being created with the default T2 Hospitality term assigned, which is causing the fields to show up on that post. Why not create a separate custom taxonomy for your CPT instead of using this default category?
Thanks,
Shane
