Tell us what you are trying to do?
I created custom fields for a custom post type. When I update any of my post entries, it works properly. But when I just need to delete an entry to leave it blank, the page does not update the entry... It basically just refreshes and leaves the input that was previously in the field.
Is there any documentation that you are following?
Is there a similar example that we can see?
What is the link to your site?
Hello, that's unusual. Can you try these basic troubleshooting steps first, to help narrow down the problem?
- Temporarily deactivate all plugins except Types, Forms, and Blocks or Views if the site uses those plugins.
- Temporarily activate a default theme like Twenty Twenty One
- Test submitting a blank field once again.
- If the problem is resolved, reactivate the theme and other plugins, one by one, testing each time until the problem returns.
- If the problem is not resolved, I'll need to take a closer look. Is it possible for me to test and see this behavior on the site? Please provide a URL where I can test this functionality.
I will activate private reply fields so you can share login credentials securely if needed.
Thank you, I'm running some tests now and will give you an update shortly.. I will be deactivating some plugins temporarily, but I will restore the site to its current state once I'm finished testing.
It seems there was a problem introduced in the latest version of Types, because after a bit of testing in my local environment I was able to replicate the same problem. When I downgraded to the previous version, Types 3.4.5, the problem was resolved. I'm asking my 2nd tier team to take a closer look, since this looks like a bug in the latest release. I'll let you know what I find out as soon as I can.
Got it. Thank you for escalating it. I look forward to a resolution. Thanks!
We've escalated this to the developers and published the following erratum post: https://toolset.com/errata/cannot-delete-existing-custom-field-values-after-types-update/
I'll keep you posted here as I receive more information.
Hi, another quick update. Our developers have informed me that this issue will be addressed in the upcoming Types 3.4.7 release. We plan to get that release ready and out to the public as soon as possible, and I will keep you informed here as I receive more information.
Hi, this issue should be resolved in the Types 3.4.7 release, which is being pushed out to clients now. If you haven't been prompted to update to the latest version, you can go to Plugins > Add New, and click the Commercial tab. Then scroll to the Toolset installer panel and click "Check for updates".
Let me know if the problem is not resolved after updating to Types 3.4.7
