I did not include a link as it would require you to create a free account and then create a new progress hidden link
Once you created it and view the new post, it would display:
Progress is based on: Repetitions
Exercise: THIS SHOULD DISPLAY THE EXERCISE WHICH IS A PARENT; IT DISPLAYS IF YOU ARE ADMIN
Date: December 9, 2022
Number of kettlebells:2 (double kettlebells)
Can I clarify, you are talking about Toolset post relationships here, rather than hierarchical pages?
And the problem arises when using dynamic sources in a block in the template for the child post that refers back to the related parent (when the child post has status private)?
The post is related to the Exercise, a Progress Update is set to private upon creation.
Once I mark the post as public, it shows the Exercise to the user.
I've performed some tests on my website with a similar setup as you've shared, but couldn't reproduce this behavior. This suggests that something specific to your website is involved here.
Can you please share temporary admin login details, along with the link to the example post page, where the parent post is not showing?
Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.
Thank you for waiting as we had some unusually busy forum queue due to the holidays.
During testing and troubleshooting, I noticed that you'll need to grant the "read_private_posts" capability to the user role "Site Registered User", so that they can see the related "Exercise" post, on the single "Note" post page, when in the 'private' state.
I've enabled it on the staging website and you can enable the same on the live/production website from WP Admin -> Toolset -> Access Control -> Custom Roles -> Site Registered User -> Change permissions -> Other capabilities.
Brilliant, thanks for that. It doesn't make sense, as the user was able to read the private post, it was the info that wasn't private that would not display. Kind of like private and public don't mix. Either way, thanks for debugging this.