Skip Navigation

[Resolved] Error when save child with conditionnal output

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

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 1 reply, has 2 voices.

Last updated by Waqar 5 years, 1 month ago.

Assisted by: Waqar.

Author
Posts
#1211679

I used a feature since a long time but since few month it doesn't work anymore, but I speak about it only today.

My problem is about conditional display of fields. When you create a group of custom fields you can add a condition to display the field only if another field have a specific value.

I worked well, but now each time I try to save my custom type post I got a white page with this message : {"output":"","errors":"","conditionals":{"#post":{"triggers":[],"fields":[],"custom_triggers":[],"custom_fields":[]}}}

I precise that my custom type is a child of post and I edit them in the post editor page. But each time I save my childs I got the white page with the message : {"output":"","errors":"","conditionals":{"#post":{"triggers":[],"fields":[],"custom_triggers":[

The only way to save my work is to disable the conditional display.

Do you know this problem ?

#1211966

Waqar
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi Guillaume,

Thank you for contacting us and I'll be happy to assist.

I couldn't reproduce this issue on my test website or find any other recent similar reports.

To troubleshoot this, I'll recommend to temporary disable all non-Toolset plugins and then check the custom post type again.

It would also be a good idea to test this with a default theme like "Twenty Nineteen", to rule out a theme or custom code conflict.

In case the issue still persists, you're welcome to share temporary admin login details in reply to this message, with the exact steps to see the error.

I've set your next reply as private so that only you and our support team will have access to it.

Important note: Please make a complete backup copy of the website, before sharing the access details.

regards,
Waqar

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.