Closed CloundNine closed 1 year ago
@sc0ttkclark I had a second client complain of this same behavior on November 7 and just tested this again on a third installation and all are behaving the same. I am rolling back my updates and stopping auto update. I am also happy to create a testing area if needed or provide any other details.
@CloundNine I'm not seeing the Bidirectional option set for those corresponding pod/fields. Can you go over those configurations and confirm those are set on both sides correctly next time you test an update for Pods 2.9.x?
Finally able to look at this again after accidentally updating pods from 2.9.8 and fielding calls from the client. I had no need for these to be bidirectional and maybe my language is unclear when I said "The related post is created but the connection is not made." I did create a bidirectional connection just in case but that didn't solve anything. I also deactivated ALL plugins except Pods and WP Rollback.
I will attempt to demonstrate on a screen capture.
https://www.loom.com/share/c4d6c1a26661435893efe917bb90c12d
Perfect screencast, thanks for getting that together. Sorry about the delay but a fix for this will be included in Pods 2.9.12.
Fixed via https://github.com/pods-framework/pods/commit/d7cfc53c607dd2532cb5fd8ee8ac371c946bfdb3
Description
CPT called Meetings has two fields for related documents (Documents is another CPT, not extended Media). After update to 2.9.9 adding these related items to pre-existing Meetings is not working as expected. The related post is created but the connection is not made.
Version
2.9.9
Testing Instructions
1 Edit existing Meeting 2 Add New in either Minutes or Agenda field. 3 Complete fields for title, date, and connect media item or upload. 4 Click Publish The "second level" window closes but the resulting record does not show as connected in the screen shot attached, the Agenda is done by searching for a documnent already loaded, for the Minutes a document was added but it's not showing and if you publish, the connection has not been made.
Screenshots / Screencast
Possible Workaround
Reverting to previous version of PODS solves the issue
Site Health Information
Pods Package