SOLUTION: I looked through Divi’s functions.php & saw that the term for the project tags is ‘project_tag’, so when I amended my $query args it now works! Thank you very much to everyone who responded 🙂 $query_args = array( ‘post_type’ => ‘project’, ‘post_status’ => ‘publish’, ‘order’ => ‘DESC’, ‘orderby’ => ‘date’, ‘posts_per_page’ => ‘3’, ‘project_tag’ … Read more
This cannot be done inside the tr tags, you need to separate this out into two stages. First collect the data ( without displaying any HTML ), then display that data. For example: $editor = new WP_Query( [ ‘posts_per_page’ => 20 ] ); // each item in this array will be a post/an array of … Read more
First, create the custom WordPress widget. This will query all the years that have at least one post for your custom post type “Meeting.” Save the following code in your theme’s functions.php file: class Meeting_Archive_Widget extends WP_Widget { public function __construct() { parent::__construct(‘meeting_archive’, ‘Meeting Archive’, array(‘description’ => ‘List Meetings by Year’)); } public function widget($args, … Read more
All the date functions reference the global $post variable, but from your code the $post variable is not being used, so that’s why the date is wrong. Try this (untested): foreach ( $total_results as $tr ) { echo get_the_time( ‘j F Y, G:i’, $tr ); }
Never use new WP_Query for the main query of an archive template. WordPress has already queried the correct posts and things like pagination are based on that query. If you want to modify that query you should use the pre_get_posts to modify the main query before it is run. The hook runs on every query … Read more
Your approach is on the right track, but there are a couple of adjustments needed to make it work as intended. The primary issue is with the scope and updating of the $last_value variable. It needs to be declared outside of the loop to maintain its state across iterations. Here’s a revised version of your … Read more
Yes, this is how it is supposed to work. The global $post variable is set quite early in the page load, at the wp hook. As you can see from the hook order, this is before the loop starts. Basically the $post object exists independent from its actual content in the database, which you retrieve … Read more
This is because have_posts() is for the main loop, and not your custom query. Prefixing each use of have_posts() and the_post() with $WatchListQuery-> will fix it: if ( $WatchListQuery->have_posts() ) { while ( $WatchListQuery->have_posts() : $WatchListQuery->the_post();
No, you did nothing wrong. It’s a known issue and in WordPress v6.1.3 and up to the current stable release as of writing (v6.2.2), it’s happening because of the following lines in get_the_block_template_html() which returns the markup for the current (block-based) template: $content = do_shortcode( $content ); $content = do_blocks( $content ); So as you … Read more
Use WP_Query directly in your WP theme template files instead of a block editor. // Define custom taxonomy (category) terms $categories = get_terms(array( ‘taxonomy’ => ‘your_custom_taxonomy’, // Change ‘your_custom_taxonomy’ to the name of your taxonomy ‘hide_empty’ => false, )); // Loop through each category foreach ($categories as $category) { echo ‘<h2>’ . $category->name . ‘</h2>’; … Read more