can you please test this in your child-theme functions.php:

function avf_alb_supported_post_types_mod( array $supported_post_types ) {
  $supported_post_types[] = 'proyectos_ma';
  return $supported_post_types;
}
add_filter('avf_alb_supported_post_types', 'avf_alb_supported_post_types_mod', 10, 1);

function avf_metabox_layout_post_types_mod( array $supported_post_types ) {
  $supported_post_types[] = 'proyectos_ma';
  return $supported_post_types;
}
add_filter('avf_metabox_layout_post_types', 'avf_metabox_layout_post_types_mod', 10, 1);

if you have opended a post / portfolio – the metabox is missing?

At the top of the window there is a “Screen Options” dropdown button that allows you to mark whether or not these features should be displayed.
Perhaps someone had accidentally removed the “Featured Image” meta field
(click to enlarge:)

first – even if the other browsers are doing it well – i would use the flex modell here for all browsers – and for the responsive case – set the items
f.e.:

#top #wrap_all .avia-gallery .avia-gallery-thumb {
	display: flex;
	flex-direction: row;
	flex-wrap: wrap;
}

#top #wrap_all .avia-gallery .avia-gallery-thumb a {
  width: unset !important
}

@media only screen and (min-width: 990px) {
  #top #wrap_all .avia-gallery .avia-gallery-thumb a {
    flex: 0 1 16%
  }
}

@media only screen and (min-width: 768px) and (max-width: 989px)  {
  #top #wrap_all .avia-gallery .avia-gallery-thumb a {
    flex: 0 1 25%
  }
}

@media only screen and (max-width: 767px) {
  #top #wrap_all .avia-gallery .avia-gallery-thumb a {
    flex: 0 1 33%
  }
}

@media only screen and (max-width: 479px) {
  #top #wrap_all .avia-gallery .avia-gallery-thumb a {
    flex: 0 1 49%
  }
}

@media only screen and (max-width: 339px) {
  #top #wrap_all .avia-gallery .avia-gallery-thumb a {
    flex: 1 1 100%  /*** here the images can grow to 100% ( first 1 indicates the item-grow ) ***/
  }
}

next question to the mods/devs on WordPress wp-includes – general-template.php ( near lines 2690 )
is that the normal setting:

function get_post_time( $format = 'U', $gmt = false, $post = null, $translate = false ) {
	$post = get_post( $post );

translate is set here to false.

The snippet from Ismael’s link placed in your child-theme functions.php ensures that only the child theme is loaded exclusively.
if you only have changes in the php – it is not necessary to have css and js child-theme files.
If you edit them too – you can change the loading in the child-theme php file . f.e. in video.php at lines 43ff:

function extra_assets()
{
	//load css
	wp_enqueue_style( 'avia-module-video', AviaBuilder::$path['pluginUrlRoot'] . 'avia-shortcodes/video/video.css', array( 'avia-layout' ), false );

	wp_enqueue_script( 'avia-module-slideshow-video', AviaBuilder::$path['pluginUrlRoot'] . 'avia-shortcodes/slideshow/slideshow-video.js', array( 'avia-shortcodes' ), false, true );
	wp_enqueue_script( 'avia-module-video', AviaBuilder::$path['pluginUrlRoot'] . 'avia-shortcodes/video/video.js', array( 'avia-shortcodes' ), false, true );
}

f.e. by replacing the load css file via:

//load css
wp_enqueue_style( 'avia-module-video', get_stylesheet_directory_uri().'/shortcodes/menu.css', array( 'avia-layout' ), false );

and then you will upload that edited css file to the shortcodes folder aswell.

By the way – concerning to the youtube plugin ( all other topics concerning to this are closed)

Now see here two example pages:
https://webers-testseite.de/goodwave/
https://webers-testseite.de/goodwave2/

the first is with the height setting of css code above and parallax background-images – ( you see a lot of parallax means bad performant page )
( a little trick avoids a white stripe under each hmiparallax section – the background-color of it is equal to the following section ! )

the second example page is with background-image set to scroll ( yes it is scroll ) and with a pseudo-container before that has inherits the same background-image – and that pseudo-container get position fixed !!
That is because background-attachment : fixed has problems not only on mobile advices but also on Safari Browsers on desktop.
to have more of the images on small screens – i set those sections to:

@media only screen and (max-width:767px) {
  .avia-section.hmiparallax .container {
    height: 100vw !important;
  }
}

is there a link to an example page?

this is pure css code – so the place to be inserted is your quick css field in enfold options – general styling.

you’re welcome. You even went the way of your own image format. It’s great that it worked out that way.

I have only looked through the contents of the folders in Enfold 4.9. There you can see the files. Since the older versions only have 3 files, it was obvious to browse through them to see if there were any differences.

hm – the min-height is calculated in icongrid.js – but it has never run into conflict on my enfold pages.
and if you look at the rendering of the page, the correct height seems to be calculated at first, but then it is converted to the wrong output.

are you familiar with the enfold debug mode?
Then please post the whole enfold shortcode of that page here – and i will import it on a test environment of mine.
Then i can better inspect – if that error is reproducable.

Next – one big different is that we have now on
enfold/config-templatebuilder/avia-shortcodes/icongrid/
4 files with one icongrid_old.css and one icongrid.css – and the difference is immense between those files.
there must be the reason for your troubles.

PS: i’m participant as you – so i do not see private Content area that you posted – including logins etc.

i do not understand the 3rd image.
if you like to add a new portfolio ( yes – even this is a custom post type ) you go and create a new portfolio.
Why don’t you create new post with new “hunde” ?
in this list there must be the new cpt’s – aren’t there?

or is image3 made this way? ( you erased the whole permalink )

why don’t you layout it you want on ( image3 ) and save the whole page as template.

you then can create a new “hunde” page – click on template and then on “hunde-Template” to insert the whole layout.

Big Advantage is that you can save these templates via Enfold (Child) – Import/Export : “Export Layout Builder Templates”

But you edit the po files ( not mo ) – after editing the po file with e.g. poedit this creates the po and mo files. Both files had to be uploaded.

btw: you can have your own child-theme lang folder and to have this active you can use in your child-theme functions.php:

function overwrite_language_file_child_theme() {
    $lang = get_stylesheet_directory().'/lang';
    return $lang;
}
add_filter('ava_theme_textdomain_path', 'overwrite_language_file_child_theme');

see : docu