Skip Navigation

[Resolved] Update Bug: existing custom fields for specific categories now req on all posts

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
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 1 reply, has 2 voices.

Last updated by Beda 5 years, 11 months ago.

Assisted by: Beda.

Author
Posts
#1204769
Screen Shot 2019-02-22 at 3.01.24 PM.png
Screen Shot 2019-02-22 at 2.55.14 PM.png
Screen Shot 2019-02-22 at 2.54.57 PM.png
Screen Shot 2019-02-22 at 2.53.58 PM.png
Screen Shot 2019-02-22 at 2.21.51 PM.png

I am trying to:Not trying to do anything new. Your update broke our site. We can't publish or edit any posts as custom fields which should only be required on certain categories are now being required on ALL posts.

Link to a page where the issue can be seen: In the admin. See screenshots. Issue is obvious and easy to reproduce.

I expected to see: Expected to be able to save a draft post that is NOT in the "Dog of the Month" category WITHOUT inputting Dog Title, but cannot do so.

Instead, I got: Was required to input Dog Title and List Title. See images. The latest screenshot uploaded shows that "Dog of the Month" is not checked off under "Categories" yet the "Dog Title" field (as well as List Title) are incorrectly required on the post.

#1204908

This is a known issue, and it's reported here.
https://toolset.com/errata/the-field-group-assigned-to-a-content-template-appears-in-all-post-types-edit-screens/
It states there it happens only with CT (Content Template) but that is not true, it happens with several other conditions as well.

I have asked the people who created that erratum to update it, however, that will not happen before Monday.

Since there is no patch or fix for it, that is not really breaking news either. You should see a fix for this by Monday or Tuesday.

Thanks and I apologise the mess.