Sounds like it could be an issue with the database and serialization of the plugin options. I’ve had problems before with plugin settings etc when moving a site using the xml export. The category templates plugin writes a lot of options to the db and they could be corrupted. As a test try creating a … Read more
I would stay stick to the function. PHP caches functions for speed and efficiency. In some situations, using a function is faster then using a variable. There are other benefits too – imagine if you changed the name of your variable – you would have to go and update every piece of code where it’s … Read more
Unfortunately all of your code is wrong. What you are doing is the same as query_posts, which should never be used. Also, never swap the main query on any type of archive page or on the home page for a custom query To create a tag page, just simply make a copy of your index.php, … Read more
Thanks again to cybmeta for his comments in my earlier question. Of course the solution is to use an archive template. The filename will be archive-foobar.php. The target URL will indeed be mydomain.com/foobar. This works fine, even though for my purposes “archive” is a misnomer. The end user never sees the word “archive”. Additionally, using … Read more
You have to add the following lines at the top of your post template file: <?php /* * Template Name: Featured Article * Template Post Type: post, page, product */ get_header(); ?> Of course replace “Featured Article” with your desired template name and the list of post types with the post types you want to … Read more
Background & Core Functionality Why a Taxonomy Path Slug Alone Produces a 404 However this slug doesnt work. mysite.com/wiki/help-topics throws a 404. WordPress does not provide a mechanism for “an archive of taxonomy terms” out of the box – that is, neither the template hierarchy nor the WP_Query/WP_Tax_Query logic support a direct display of terms … Read more
you can do it like this: //add movies_view to query vars add_filter(‘query_vars’, ‘my_query_vars’); function my_query_vars($vars) { // add movies_view to the valid list of variables $new_vars = array(‘movies_view’); $vars = $new_vars + $vars; return $vars; } then add a template redirect based on that query_var: add_action(“template_redirect”, ‘my_template_redirect’); // Template selection function my_template_redirect() { global $wp; … Read more
I suggest creating 3 files 1) regiontemplate-country.php 2) regiontemplate-city.php These 2 will contain the templates for country & city, then 3) taxonomy-region.php In this file, add the code to load the appropriate template <?php $term = get_term_by(‘slug’, get_query_var(‘term’), ‘region’); if((int)$term->parent) get_template_part(‘regiontemplate’, ‘city’); else get_template_part(‘regiontemplate’, ‘country’);
Correct, there is no PHP templating engine built into WordPress. This does however give you the flexibility to use a templating engine such as Twig or Blade (and I have worked on sites using each of those), or even completely headless using the REST API.
You could just include it in your functions.php: if ( ! is_admin() ) { include ABSPATH . ‘wp-admin/includes/template.php’; } Or better (as suggested by @Lance Cleveland in the comments): if ( ! function_exists( ‘wp_terms_checklist’ ) ) { include ABSPATH . ‘wp-admin/includes/template.php’; }