OK so, I cannot officially suggest or support using Views in an AJAXifieid call as we very well offer a PHP API but not a JS API.
See also https://toolset.com/forums/topic/loading-views-with-ajax/ in regard.
There are also interesting solutions at https://toolset.com/forums/topic/ajax-load-view/
In some minimal steps, you'd:
1. create a JS file (lets say in your Child Theme) where you add something like this:
Query(document).on('click', '.some-element', function(e){ //trigger element
jQuery.ajax({
method: 'post',
url: object_name.ajaxurl,
data: {
action: 'my_custom_php_function',
}
}).done(function(msg) {
// Do something when done
});
e.preventDefault();
});
2. Enqueue and localize the script with something like this:
wp_enqueue_script('string-handle', get_template_directory_uri() . '/string-handle.js', array('jquery'), '', true);
wp_localize_script('string-handle', 'object_name', array('ajaxurl' => admin_url('admin-ajax.php')));
3. Create a Function that does the PHP magic, let's say
function my_custom_php_function(){
$out = do_shortcode('[wpv-post-title item="1"]');
echo $out;
}
4. Add that function to your localized script with something like
add_action('wp_ajax_my_custom_php_function', 'my_custom_php_function');//note that here the hook is wp_ajax_, and my_custom_php_function is the name of your function, so you must change that.
5. Add an HTML element with class some-element to your site and click on it, this will show in the requests that you fired an AJAX request to function my_custom_php_function which then returns post title of item 1.
Now, this requires a post object to be passed no matter what, so if you have a view that somehow relies on the current displaying post, then you'd need to pass that either to the ShortCode, or when using the function to render View results, as the arguments.
How you find the corresponding "context" to pass, generally a post ID to relate to, probably, depends on where and how this is used.
I think in your case it could be asking for displaying related posts to the currently shown page, and hence you could try get_queried_object or get_queried_object_id of WordPress:
https://developer.wordpress.org/reference/functions/get_queried_object_id/
This can help to provide the current posts or pages context, from which you can extract the data needed to pass to the view.
Other than that I could actually not imagine any need of context, as the view will otherwise follow its internal settings.
Does this help to proceed?
