You can try to store $wp_query in a cookie or in a session variable. global $wp_query; setcookie(‘my_wp_query’, $query_string); or global $wp_query; $_SESSION[‘my_wp_query’] = $query_string; and use that in you ajax function.
Something like this if you want to call mytemplate.php: get_template_part( ‘template’); Or something like this if you want to call content-mytemplate.php: get_template_part( ‘content’, ‘mytemplate’ ); I hope that this will help you.
I think you have to enter the_post();, after have_post(),for more information on get_template_part(); refer to codex
You don’t reuse a specific page’s data via get_template_part, you query for a specific page’s data and use get_template_part to output the result. Look at how any of the core-bundled themes use get_template_part within the loop to output the main query for an example. Query for the page: $query = new WP_Query( array( ‘post_type’ => … Read more
PHP (unlike HTML) is not meant to be used as content markup language. It is server–side language with too much access. It is very challenging to safely and securely treat PHP as part of content. For basic example — what if one of your authors writes PHP code in a post which amounts to “make … Read more
How to unregister sidebar for template_part?
While there are some WP–specific solutions that track template files, for complicated projects pretty much the only reliable list is using get_included_files() PHP function at the end of page load. It would give you everything, including WP core, but filtering it down to theme is relatively easy.
Copy the file to your child theme, In your child theme, create a template and name it what ever you want, e.g content-child.php Now you can replace lib/login/register.php with your new template: <?php get_template_part( ‘content-child’, get_post_format() ); ?> It should work.
Usually the format you see in themes are content-{$post_format-term}.php or content-{$pagename}.php, but it is not restricted to this formats. The naming convention can also differ to your liking as long as you keep it out of normal template hierarchy and then use get_template_part to call it correctly. These are not self standing templates, they cannot … Read more
Using require_once for parent-directory not working but is working in sub-directories