all custom fields appearing on child posts (not just the assigned ones).

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.

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)

Tagged: Setting up custom fields, Types plugin

This topic contains 6 replies, has 2 voices.

Last updated by Beda 6 years, 2 months ago.

Assisted by: Beda.

Author

Posts

July 23, 2018 at 6:37 pm #953805

jamesH-8

Screen Shot 2018-07-23 at 11.36.42 AM.png

Event though custom fields are uniquely assigned to all templates and post types, when trying to add a child post via the parent post it offers every available custom filed. This makes it extremely confusing for the client. This looks to be new since you started using a lightbox for this..

In the provided screenshot it should only offer the title and image field. It show a ton of fields.

July 24, 2018 at 11:19 am #954404

Beda

Right, I confirm that the Child Post table does not listen to any conditions in the Fields settings but the post type.

Not even single field conditions seem to apply.
Reported as a BUG.

Thanks for the heads up.

July 24, 2018 at 4:01 pm #954585

jamesH-8

How do we fix this crucial issue?

July 25, 2018 at 5:48 am #955382

Beda

You would need to wait for the fix to be pushed.
This will happen as soon the developers will fix this problem

For now, I cannot provide any other workaround unfortunately

July 25, 2018 at 9:47 am #955448

Beda

I just saw that single fields respect the condition set by other single fields.

So this is maybe how you can workaround for now - but note, the Fields won't use the AJAX to show/hide when based on other fields values, as they do usually in the backend.

I reported this as well.

August 3, 2018 at 9:49 am #1072517

Beda

This will be fixed in the next release.

September 18, 2018 at 6:10 am #1110204

Beda

This is resolved in the latest Toolset Plugins updates

Thanks for your patience!