This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the custom field value is not saving if the user had a conditional for that field and then removed the conditional field that is required.
Solution:
I was able to identify this bug and submitted it to our development team to fix, however no fix has been published yet.
This support ticket is created 5 years, 5 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.
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.
This page has a lot of custom fields on it. However, on the backend (Its a custom post type called cafe) I am unable to save some of the custom fields. Some save whereas some dont.
We need to know what fields do not save.
Then, we need to know if after either removing or updating the 17 outdated Plugins, the issue still happens.
Note these include Toolset as well.
Then, if this issue still happens, we can check if it is a conflict with another plugin or theme by disabling them one by one on a test site.
If after the issue still persist, I would suggest to narrow down the fields that cannot be saved and try to replicate that locally (we can do that)
If then we can see the issue we can fix it as it would be a bug, otherwise, we will need to see how to best resolve the problem on site.
I have updated all plugins and turned off all plugins except types and the issue persists.
Please go here:
hidden link
There are lots of fields so I will choose a few for you to test. In the 'Top section' 'Cafe Title' saves normally. However in the 'Drinks section', 'Drinks main text' does not save.
I figured out the issue. I had a checkbox field. The other fields would only display if that field was ticked. However, when I deleted that checkbox field, the other fields then automatically appeared. However, because they still had their conditional logic set up this was for some reason stopping them saving even though they were visible. I would consider this a bug in Toolset.
The checkboxes have been removed from the field groups, thats what has created the issue. However, they still remain as a field. Once the field is deleted fully then the issue resolves. For example you can see the remaining fields in 'Bites' have a conditional set up based on a field that is not in that field group.
SO to get this clear, the bug is if you have a conditional and then you remove the field that activates that conditional then this would be the result?
