Sorry @Guenni007 but I tried: nothing worked. Any other suggestion?

Hi @Guenni007. yes the “Lightbox Modal Window” is checked. I now just uploaded the page template where I activated the html for the window I need. It’s the link you find at the right-bottom corner of teh page (Definitions-> when you click on the word a popup should come out). The style sheet is a specific one named “immas-style.css” and the function is written in the functions.php of my child theme

function popup_inline() { ?>
<script type="text/javascript">

//.on('load') is used when jQuery migrate is disabled
jQuery(window).on('load', function () {
    jQuery('.open-popup-link').magnificPopup({
        type:'inline',
        midClick: true,
        closeBtnInside:true
    });
});

</script>
<?php 
}
add_action('wp_footer', 'popup_inline');

Yes please close the topic!

Thanks Guenni007, I actually did change my settings in the browser, allowing video and audio. However still the sound is not played. I tried with Firefox Chrome and Safari, and still the audio is not audible.

Thanks Ismael, I will check the two articles you mentioned!

Ok I don’t understand. I use Firefox, but now I tried with Chrome as well. Although audio is enabled via functions.php, AND I have interacted with the domain (click) OR the video with sound has been previously played with sound, I still don’t hear anything.

Also the same thing happens if I add a direct link to the .mp4 uploaded to my server.

Is there any method to bypass the issue? My client wants specifically a video he created (the one that is in the link you received) which has sound.

Thanks for help

Thanks Ismael!! Sorry for the late reply. The problem is solved! I understand now where was the problem.
you can close the ticket now.
Great support as usual!

Yes I removed the archive-projects.php but nothing happened. Give me one hour to upload the web site to a temporary domain so that you can access. I will give you the access details and specify the pages. Thanks

Hi Ismael, sorry for the late reply but I was ways the whole week.
I did two attempts following your suggestions, but didn’t work. Here the code for each one.
First of all I created a blog page where the standard post should be visible, and I set the child theme options for blog layout as a list (that’s how I want to see my standard post). Now the idea is that if I select a specific term taxonomy from the custom type posts (projects) I want them shown in a grid format.
Here my two attempts to do it.

ATTEMPT 1
I used the is_post_type_archive function within the archive-project.php, simplifying it for my purposes:

 //above there's the code for handling the header, which I didn't change
		<div class='container_wrap container_wrap_first main_color <?php avia_layout_class( 'main' ); ?>'>
			<div class='container template-blog '>
				<main class='content <?php avia_layout_class( 'content' ); ?> units' <?php avia_markup_helper(array('context' => 'content','post_type'=>'post'));?>>
					<?php 
						$tds =  term_description(); 
						if($tds)
						{
							echo "<div class='category-term-description'>{$tds}</div>";
						}
					?>
                    <?php
                    if ( is_post_type_archive( 'projects' ) ) {
          				global $posts;
                        $post_ids = array();
                        foreach($posts as $post) $post_ids[] = $post->ID;
                        if(!empty($post_ids))
                        {
                            $atts   = array(
                                'type' => 'grid',
                                'items' => get_option('posts_per_page'),
                                'columns' => 5,
                                'class' => 'avia-builder-el-no-sibling',
                                'paginate' => 'yes',
                                'use_main_query_pagination' => 'yes',
                                'custom_query' => array( 'post__in'=>$post_ids, 'post_type'=>get_post_types() )
                            );
							/**
							 * @since 4.5.5
							 * @return array
							 */
							$atts = apply_filters( 'avf_post_slider_args', $atts, 'archive' );
                            $blog = new avia_post_slider( $atts );
                            $blog->query_entries();
                            echo "<div class='entry-content-wrapper'>".$blog->html()."</div>";
    					}
                   
                    ?>
				<!--end content-->
				</main>

ATTEMPT 2
I still have an archive-projects.php which is the exact copy of archive.php
I added to my functions.php the following code:

add_filter('avf_blog_style','avia_change_category_blog_layout_2', 10, 2); 
function avia_change_category_blog_layout_2($layout, $context){
if($context == 'archive-projects') $layout = 'blog-grid';
return $layout;
}

In all 2 attempts, the blog layout (list) set in the child theme options overwrites the codes for the archive-projects.php. So if I click on a term taxonomy of the custom type posts, they appear as a list, like the blog page instead of appearing as a grid.
Could you help me please?

• This reply was modified 4 years, 1 month ago by elenapoliti.

Hi Ismael, I got it. The code I used is as follows (I put it in the functions.php). However I got into a new problem:

My two pages, have the content element ‘blog posts’ where I show all the categories. Programatically by the below code the two pages show different posts according to the acf field = year (anno)

If however I click on the category link (hence filter by category) the category archive is mess up. I checked and something in the function below enters in conflict with the category archive. Do you have any suggestion?

I copy in the private section the link to the test page

add_filter('avia_post_slide_query', 'avia_post_slide_query_mod',10, 2);
function avia_post_slide_query_mod($query, $params) {
	$posts = get_posts($query);
	$today_year = date('yy');
	$two_years_ago = $today_year - 2;
	$current = array();
		foreach( $posts as $post ) {
			$meta = get_post_meta($post->ID); //acf fields are saved in post meta
			$acf_year = $meta['anno'][0]; //get the value of the field needed (anno=year)
			if (is_page(112)){
				if($acf_year >= $two_years_ago & $acf_year <= $today_year) {
				$current[] = $post->ID;
				}	
			}
			else if (is_page(204))	{
				 if($acf_year < $two_years_ago) {
				$current[] = $post->ID;
				}	
			}
		}
	$query['post__in'] = $current;
	return $query;
}

• This reply was modified 4 years, 2 months ago by elenapoliti.

Thanks Ismael. Just one question: in order to pass the new array as a WP query where the array is built as you suggest $date_query = your_array();
should I use $date_query = AviaHelper::add_date_query( $date_query);
or should I use $query = new WP_Query( $date_query ); ?

And, if I have a custom field named “year” in which I actually write the year of the post (not the year when the post is published) can I still use the
$query = new WP_Query( $args ); within the postslider.php? Because maybe I can simply use the custom field to filter the posts

Thanks

Thanks Ismael. usually I manually disable the template builder elements as in the past the “Load only used elements” options was crashing some pages. However I tried it now and its works. Still there are a few css / scripts that I don’t need on this specific page, but thanks for pointing out where I can find those!

Great @guenni007, it’s a good compromise! I just put it in the functions.php with a conditional setting on which page the function should be triggered and it works.

Thanks Ismael, I am sorry for having left this ticket open. I solved the problem with Search&Filter.

For future reference, I created a filtering form with S&F. Then I added the form to a widget (with the plugin in the widget area it appears the S&F). In the 1/5 column I added the widget just created. The trick was adding a further shortcode just after that, simply as text :
[searchandfilter id=”243″ action=”filter_next_query”]

In this way the plugin can filter the blog grid with an ajax request, in a similar way to what happens with the masonry filter.

You can close the ticket. Thanks

Maybe it’s better that I open a new ticket for my question above