The issue here is that the user has a button on their parent post that can be used to navigate to the child post. This button is passing the url to the child page.
Solution:
In this case we can just use the shortcode.
[wpv-post-title id="[wpv-search-term param='parent_post_id']"]
Now this will only work if the parent id is being passed in the url
Problem:
The client has a set-up where, from a parent post, a user can add a child post via a link to a front-end Toolset Form.
The particular requirements for this project are that only a logged-in user should be able to see and submit the child post form. Guest users should see a login/register form instead, and then continue to see and submit the child post form.
Solution:
There are two problems here.
The first is that guest users who register are not automatically logged in, they would register and be redirected to a log-in page, and then the flow would be interrupted.
The second is that, even if we add code to automatically log in users who register and then present them with the child post form, the URL parameter that identifies the parent is lost.
Problem: I would like to use the same View in multiple places on the same page, but I want to avoid unique IDs.
Solution: Use wpv-attribute to help generate that unique ID. For example, let's say you use the same View in two places on the same page. Add the placement attribute, and set some unique value for each View:
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
