Replies: 8 comments
-
Quick follow up - you only actually loose the bi-directional settings on one of the Pods. I suspect it's because they're created in sequence, and the second Pod hasn't yet been created. |
Beta Was this translation helpful? Give feedback.
-
Bidirectional field config is storing the related field ID (post ID), so it's possible it's not exactly as you're seeing or perhaps it's a lucky import :) |
Beta Was this translation helpful? Give feedback.
-
Is there an issue to be extracted here? |
Beta Was this translation helpful? Give feedback.
-
I don't think we can solve this one pre-migration to storing keys in wp_podsrel instead of IDs. |
Beta Was this translation helpful? Give feedback.
-
Just a note, this issue has existed as long as Bi-directional relationships and Packages have co-existed. (Even back to 1.x) |
Beta Was this translation helpful? Give feedback.
-
Brainstorming... keep track of the bidirectional relationship fields upon 'migrating' and as a last step, re-touch all those bidirectional fields to force the connection? |
Beta Was this translation helpful? Give feedback.
-
@jimtrue is this still a bug? Is there any way to export/import with bi-directional information retained? |
Beta Was this translation helpful? Give feedback.
-
@vpfaulkner: As @sc0ttkclark notes above this will not be able to be corrected until Fields Objects are a part of Pods. In most cases, honestly, I've not had issues with this and I do package migrations constantly as part of replicating bugs from GitHub. Typically once you visit one of the configurations it corrects itself in the other. |
Beta Was this translation helpful? Give feedback.
-
When I use the Migrate Packages component to export and import my pods, the Bi-directional information is lost from Relationship fields. It's repeatable:
Workaround: Just make sure to add back your bi-directional settings in each of the Pods once you've imported. No biggie :)
Beta Was this translation helpful? Give feedback.
All reactions