Skip Navigation

[Resolved] Since Types 3.2.5 custom fields are not respecting their post type restriction

This thread is resolved. Here is a description of the problem and solution.

Problem:
With the update to Types 3.2.5 custom field groups are not respecting their display settings.

Solution:
This was a bug introduced in Types 3.2.5 which is resolved by updating Types and Access.

This support ticket is created 5 years, 11 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.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 5 replies, has 2 voices.

Last updated by Jonathon Hanten 5 years, 11 months ago.

Assisted by: Nigel.

Author
Posts
#1202430

I expected to see: a custom field group only showing up on the post type it was assigned to (in this case posts), but the field group is showing on every post type throughout the whole site. My staging site is still running 3.2.4 and this problem is not occuring. Our live site is running 3.2.5 and the custom fields are showing up everywhere.

#1202475

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Jonathon

I have one other user reporting the same. I cannot reproduce the issue locally, and visiting their site on the backend I couldn't see the problem either, meaning it is likely a caching issue.

If you have a caching plugin can you flush the cache, and with your browser can you clear the cache and do a hard reload on the post edit screens.

Let me know if that fixes the problem.

#1202494

I cleared the cache and that didn't make a difference, but when I rolled back to 3.2.4 the problem went away so I'm still thinking this is a coding error. I just noticed that 3.2.6 is out do you happen to know what changed between .6 and .5?

#1202518

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

There was a fix for a different issue with Custom Field Groups (https://toolset.com/errata/cannot-edit-or-see-toolset-custom-fields-if-using-access-for-any-role-below-administrator/), as well as an issue some users were experiencing with the installer.

I can't tell you if it will fix your issue, because I've been unable to reproduce it, but it would certainly be helpful to know if you update whether it does.

Please let me know.

#1202579

I can confirm that 3.2.6 did not fix my issue. I have disabled all plugins except for Toolset Types and the problem remains. I have also changed out my theme and cleared the cache again and the problem remains.

This is only happening for my custom fields that are linked to posts. All other custom fields related to custom post types are working as expected. While testing I change the field group to other custom post types and pages and everything worked as expected. Luckily when I changed the field group back to posts only it is now working correctly. Maybe you can make this suggestion to your other user.

Jonathon

#1202640

My issue is resolved now. Thank you!