Problem:
Option to change number of posts per page when using archive
Solution:
The 'wpv_filter_query' hook will work for views not for archives. If you want to filter archive query arguments on fly either you will have to use pre_get_posts hook or the 'wpv_action_apply_archive_query_settings' hook.'
Problem:
How to display dynamic content on pages based on a selection on the landing page
Solution:
There is no such feature available to add URL param to nav menu items. You can use the WordPress default hook "wp_get_nav_menu_items" to do any amendments with the menu item links.
Problem:
Parent view not rendering on frontend - how to display parent post image
Solution:
To display parent custom field image in one-to-many relationship you can display it directly using image block. You can add the image block and selected the parent post.
The issue here is that the user wanted to restrict their relationship forms relationship fields to only the posts that the user created.
Solution:
There is an option on the relationship form fields that allows you to only pull the options for the current user. What this means is that they will only see a list of options that they are the authors for.
Under the filtering option you should be able to set it to get only the current user's posts.
Problem:
pass value of a post:custom field thru to next page as a hidden parameter
Solution:
Toolset uses the WordPress standard to store the custom fields. The custom post type custom fields will be saved to postmeta table.
You will have to check how you can get the custom field value either using the get_post_meta() function but to get the custom field value you will require the post ID. You have to find how you will pass the post ID so that based on the passed post ID you can get any custom field value using get_post_meta() function based on the passed post ID.
