I have a site under development. One of the CPT's is set up as a child of one other CPT. I'm suddenly experiencing two issues:-
1. when I try to add a child link shortcode to a CT, the page containing the form (which contains the parent selector) can't be found. If I add the shortcode manually, the user can see the form on the frontend and it works as it should.
2. Until now I've used this format to display the value of custom field 'final-choice' from the parent post type 'owner':-
I didn't think any of the upcoming changes to the way post relationships will work had been implemented yet or have I missed something? Is there an explanation as to why I suddenly have these issues? If the behaviour under point 1 isn't expected, what can I check/try to ascertain the cause please?
2. can you share the link to the thread where you found that code.
It seems to be a workaround, as that still addresses the old relationship fields.
The code that "works" for you just calls the proper field directly by post meta, instead of with our $parent syntax.
but I am not aware that this is broken.
Yes - I've followed the same way to display the parent custom field value and its working for me.
Could you please share debug information as well as problem URL where I can see the issue?
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I would additionally need your permission to de- and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important. If you agree to this, please use the form fields I have enabled below to provide temporary access details (wp-admin and FTP).
I have set the next reply to private which means only you and I have access to it.
For some reason I didn't get the last two responses in this thread (?). In the meantime, I've tested this on a vanilla site and it's OK so I think there's something awry my end where I first had the issue. If I need to I'll come back to you. Thanks for your help.