Bi-directional field error #6832
Replies: 5 comments
-
Sounds like you need to, at least temporarily, disable the required option on the field at the other end. Have you seen the page on how relationship fields are saved? The way it works is not very obvious so you might want to make sure you're reading that table right. |
Beta Was this translation helpful? Give feedback.
-
Disabling the required option resolves the problem. But the field needs to be required. I tried to replicate the issue by creating a new relation and removing the related item in the backend but that works as expected. I have no idea how this ever happened in the first place 😕 For now i will disable the require option and save all the items and enable the require option again. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
@KoenRijpstra I'm glad to help and to hear you got this resolved. |
Beta Was this translation helpful? Give feedback.
-
I'm finding myself getting this issue, my steps to reproduce are:
|
Beta Was this translation helpful? Give feedback.
-
Got the same problem here with a project, though it doesn't happen all the time... trying to find out when it does and when it doesn't. |
Beta Was this translation helpful? Give feedback.
-
When i save a custom post type with a Bi-directional field i get the following error:
The Franchise field is required and cannot be removed by the Vestigingen field
The field shows 1 connected post but in the
_pods_vestigingen
meta field there are 2 post ids. One of those ids doesn't exist anymore in the wp_posts table. Is it possible that if I remove an item the relation field won't get updated?Running version 2.3.18
Beta Was this translation helpful? Give feedback.
All reactions