Anyway the fact is that there are empty p-tags:

and that is because of the rule above the reason for different behavior.

See here your first link markup:

Edit: That was a little too much urge to communicate here in this answer – therefore : away with it.
The above is enough for your solution.

and here you see next advantage – the columns “width” 1/3 has no influence – what do you think would happen if i declare this for large screens?

@media only screen and (min-width:1800px) {
  .three-two-one .entry-content-wrapper .flex_column {
    flex: 0 1 15%;
  }
}

Well best would be to ignore Enfold Settings and play a bit with flexbox layout.

on my testpage you see on top the flexbox – and in the grey color-section this is columns declaration on default.
i gave to the top color-section a custom-class of: three-two-one :lol
the top columns ( i take 1/3 – but this is not important ) – but take individual height please

To play a bit with justify-content it would be nice to only have columns in that container and no :before and :after pseudo elements
(thats the first rule)
Put this to quick css then:

.three-two-one .entry-content-wrapper:before,
.three-two-one .entry-content-wrapper::after{
  display: none;
}

.three-two-one .entry-content-wrapper {
  display: flex;
  flex-flow: row wrap;
  justify-content:  space-between;
  align-items: stretch
}

.three-two-one .entry-content-wrapper .flex_column {
  flex: 0 1 28%;
  margin:0;
  padding: 0;
  margin-bottom: 3% 
}

/****  your tablet definitions - play with the values as you like  ***/
@media only screen and (min-width: 768px) and (max-width: 989px) {
  .three-two-one .entry-content-wrapper .flex_column {
    flex: 0 1 47%;
  }
}

/*** this is not necessary because on that screen-width the Enfold default is 100%  ***/
@media only screen and (max-width: 767px) {
  .three-two-one .entry-content-wrapper .flex_column {
    flex: 0 1 100%;
  }
}

you can see here the test page: https://webers-testseite.de/3columns/

_____
here a nice overview to flexbox layout: https://css-tricks.com/snippets/css/a-guide-to-flexbox/
here a playground to get a feeling on what could be done ( sorry this is german page – but you can play with checkboxes on bottom ) : https://www.mediaevent.de/css/display-flex.html

on the last link for example see the part with : justify-content.
now you see why i do no want to have before and after containers in it – these would be handled like flex items .
The align-items : stretch results in “equal height containers” etc.

A really might “tool” – isn’t it ?

is there a link to see – it is easier to give advice then

with that background-image it is hard to recognize that there is a hamburger to click.
And i would not show the advanced layerslider on responsive case ( mobile, small screens )

maybe you style the colors a bit and make the line-height of the burger not shrink with the script:

.header_color .av-hamburger:not(.is-active) .av-hamburger-inner, 
.header_color .av-hamburger:not(.is-active) .av-hamburger-inner::before, 
.header_color .av-hamburger:not(.is-active) .av-hamburger-inner::after {
	background-color: #f4f1cb;
    -webkit-filter: drop-shadow(1px 1px 3px #000);
	filter: drop-shadow(1px 1px 3px #000);
}

.responsive #top #header_main > .container .main_menu .av-main-nav > li > a {
  line-height:82px !important;
} 

can you post your child-theme functions.php here!

you can see results here on my test-page: https://webers-testseite.de/portfolio/
Edit : i’m still experimenting a bit – so the example page could be not of the intended function.

maybe Ismael knows a method to do it for that ajax setup too. Without that selector only for non ajax grids the click on ajax has two click events and does open first the window above the grid – but directly moves to the single portfolio.

• This reply was modified 2 days, 14 hours ago by  Guenni007.

click on one link please of the blog ( on the bottom or text )

yes i changed it allready on my post above – transmission errors ;)

did you make sure you left the top <?php up there ?

The purpose of a child theme solution is to leave the parent elements untouched – my code above works without changing a parent element file.

Ishmael’s code from Back then (2016) certainly worked; only the function: unregister_taxonomy() has probably become part of the parent source code by now. And that would end in an error because: A redeclaration is not possible – thats why i wrote that i had renamed the function to something different.

I have tested it by myself and you see that even on this part there is book categories.
By the way, if you have not intentionally disabled it – you can edit the functions.php via the dashboard.
Dashboard – Appearance – Theme Editor
on the right side you can choose the file which you like to edit. On default there are only two files ( style.css and functions.php)

we only had to rename the function to let it work – because a redeclaration of a function that already exists is not possible : so code for you to try:

/**** Portfolio umbenennen im Dashboard ****/
add_action( 'init', 'unregister_taxonomy_for_custom_label', 30);
function unregister_taxonomy_for_custom_label(){
  global $wp_taxonomies;
  $taxonomy = 'portfolio_entries';
  if ( taxonomy_exists( $taxonomy))
    unset( $wp_taxonomies[$taxonomy]);
}

// portfolio args
add_action( 'init', 'init_reg_portfolio', 50 );
function init_reg_portfolio() {
  add_filter('avf_portfolio_cpt_args', 'avf_portfolio_cpt_args_mod', 50, 1);

  $tax_args = array(
    "hierarchical" => true,
    "label" => "Books Categories",
    "singular_label" => "Books Category",
    "rewrite" => array('slug'=>_x($permalinks['portfolio_entries_taxonomy_base'],'URL slug','avia_framework'), 'with_front'=>true),
    "query_var" => true
  );

  $avia_config['custom_taxonomy']['portfolio']['portfolio_entries']['args'] = $tax_args;

  register_taxonomy("portfolio_entries", array("portfolio"), $tax_args);
}

add_action( 'after_setup_theme', 'init_reg_portfolio' );

function avf_portfolio_cpt_args_mod($args) {
  $labels = array(
    'name' => _x('Books', 'post type general name','avia_framework'),
    'singular_name' => _x('Books Entry', 'post type singular name','avia_framework'),
    'add_new' => _x('Add New', 'book','avia_framework'),
    'add_new_item' => __('Add New Book Entry','avia_framework'),
    'edit_item' => __('Edit Book Entry','avia_framework'),
    'new_item' => __('New Book Entry','avia_framework'),
    'view_item' => __('View Book Entry','avia_framework'),
    'search_items' => __('Search Book Entries','avia_framework'),
    'not_found' =>  __('No Book Entries found','avia_framework'),
    'not_found_in_trash' => __('No Book Entries found in Trash','avia_framework'),
    'parent_item_colon' => ''
  );

  $args['labels'] = $labels;
  return $args;
}
/*** Ende ****/

Well you can change the label and on permalinks the slug you see in the url.
See here for Label: https://kriesi.at/support/topic/possible-to-rename-portfolio-entirely/

and here is the child-theme usage : https://kriesi.at/support/topic/renaming-the-portfolio-custom-post-type-child-theme-issues/#post-564363

on the code above you can add as many changes you like to have semi-colon separated ( this part: replaceElementTag…
The function on top is to transfer all attributes to the new tag.
see here explanation: https://kriesi.at/support/topic/widget-tags-remove-h3/#post-1016082

hm try this instead:

function shift_link_to_grid(){
?>
<script type="text/javascript">
(function($) { 
	$(document).ready(function() {
		$('.grid-entry').on('click', function() {
			window.location.href = $(this).find('.grid-image').attr('href');
		});
	});	
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'shift_link_to_grid');