Thank you for getting in touch. However I don't think the post parent's post title is stored in a custom field?
If the using [wpv-post-title] returns the correct post title of current post then you should be able to get the correct parent title by following this concept using the item attribute using the format @{relationship-slug}.{relationship-role} https://toolset.com/documentation/user-guides/views-shortcodes/item-attribute/
However given that you are using the $parent value instead i'm assuming that this is a hierarchical post type relationship ?
Using [wpv-post-title] returns the page title not the specific CPT post name for the favourite row.
Basically this is the customisation for each row, when showing a users favourites.
I thought maybe we could pass the Toolset shortcode an ID to tell it which post title to show instead? Since the Toolset plugin can't figure it out at the moment?
I realise we can use attribute item to pass the ID, problem is Favorites doesn't let us pass the ID only the post title.
Regarding the relationship I am using a one to many. I guess id probably decsribe it as a hierarchical relationship (I am not sure if this is an actual setting though?). It involves just 2 post types.
The plugin I am specifically using is hidden link - its been suggested a few times on Toolset forums as an option for managing user favourites. Curious if this questions ever been asked but I couldn't find anything on it.
Using [wpv-post-title] returns the page title not the specific CPT post name for the favourite row.
Basically this is the customisation for each row, when showing a users favourites.
I thought maybe we could pass the Toolset shortcode an ID to tell it which post title to show instead? Since the Toolset plugin can't figure it out at the moment?
I realise we can use attribute item to pass the ID, problem is Favorites doesn't let us pass the ID only the post title.
Regarding the relationship I am using a one to many. I guess id probably decsribe it as a hierarchical relationship (I am not sure if this is an actual setting though?). It involves just 2 post types.
The plugin I am specifically using is hidden link - its been suggested a few times on Toolset forums as an option for managing user favourites. Curious if this questions ever been asked but I couldn't find anything on it.
Using [wpv-post-title] returns the page title not the specific CPT post name for the favourite row.
Basically this is the customisation for each row, when showing a users favourites.
I thought maybe we could pass the Toolset shortcode an ID to tell it which post title to show instead? Since the Toolset plugin can't figure it out at the moment?
I realise we can use attribute item to pass the ID, problem is Favorites doesn't let us pass the ID only the post title.
Regarding the relationship I am using a one to many. I guess id probably decsribe it as a hierarchical relationship (I am not sure if this is an actual setting though?). It involves just 2 post types.
The plugin I am specifically using is hidden link - its been suggested a few times on Toolset forums as an option for managing user favourites. Curious if this questions ever been asked but I couldn't find anything on it.
Thanks for the further details. I understand now, the [wpv-post-title] shortcode is getting the ID of the current page rather that the post in the favourites.
You can manually pass the ID of the parent post into the shortcode but it won't be dynamic and I believe a similar issue will happen with using a view given that in order to filter correctly the view needs the correct ID however the Favourite post plugin isn't providing the ID for us to use instead we are getting the current page's ID.
Perhaps you can check with the team of the Favourite Post plugin to see if they have a way to get the id's of the posts that they are displaying.
If we get this then we may be able to use it to filter the view and get the parent post title.
As well as where on the frontend I can preview any changes that are made in the editor. This way I can work through to understand the flow of data on the plugin to see if there is a solution to the issue you are experience.
