as a participant I can’t see your links listed in the private window; I would also try with background images, but inherit them into a pseudo container, and then execute the hover styles with it. This has the advantage that the foreground content is not affected.
With parallax backgrounds I think you have an extra container anyway.

by the way – the pseudo container is a good solution to hamper the behavior on safari browsers with attachment fixed.

see here: https://webers-testseite.de/jb84/

• This reply was modified 1 year, 1 month ago by Guenni007.

Einige Sicherheitsplugins unterbinden gerne den Theme-Datei Editor. Meist geschieht dies z.B. via wp-config.php Eintrag.

einer dieser beiden oder sogar beide könnten Einfluss nehmen:

define( 'DISALLOW_FILE_EDIT', true );
define( 'DISALLOW_FILE_MODS', true );

löschen oder auf false setzen

So – it seems to work with the attribute of Ismael, just not when you insert it there afterwards via script.
It must be hardcoded in the class-form-generator.php ;)

the attribute readonly works even if you add it via script.

Today i do not see the errors concerning to FA. And believe me – I have to use the Developer Tools very intensively to investigate your site; but today this error message is no longer present.

after one cycle the transition is without this “blinking” – so probably Ismael is right – after loading the images of the first cycle everything is fine.

try that instead:

function remove_text_input_mode_on_datepicker(){
?>
<script type = "text/javascript">
window.addEventListener("DOMContentLoaded", function () { 
	(function($){
		$('.avia_datepicker').each(function() {
			$(this).attr('readonly','readonly');
		});  
	})(jQuery);
});
</script>
<?php
}
add_action( 'wp_footer', 'remove_text_input_mode_on_datepicker', 20 );

if you need it now – you can have here a solution from ismael:
https://kriesi.at/support/topic/date-picker-form-issue-mobile/#post-1419995

i can not confirm this. Even on a iPad Mini 3 (iOS 12.5.7) it works!
Only annoying thing is that the keyboard opens on that to input – but this is allready in the next update fix ( 5.6.7):

tweak: added inputmode=”none” to datepicker in contact forms to hide default mobile keyboard

that is why i have added the comment in the css code-

/****** hover Verhalten abschalten für den responsiven Fall ********/
/****** bei Querformat iPad Pro 12,9inch = 1367px / bei iPad Pro 11inch = 1195px ********/
/****** bei Querformat iPad  10,2inch = 1081px / etc. pp ********/

your tablet has: 1080px width in landscape mode
so replace that line:
@media only screen and (max-width: 989px) {
to:
@media only screen and (max-width: 1081px) {
because you want that it will work on 1080px

___________________

What do you think will happen if you don’t put all your CSS in a media query?
So you don’t put the 1080px limit there?
Then I think it will apply everywhere – for all screen widths ;)
(remember to remove the last bracket if you want to do it that way).

@media only screen and (max-width: 1081px) {
       /***** the codes inside the media query ****/
} /**** the closing bracket *****/

can you please try this in you quick css:
( all here with your custom-class – if you want that globaly – ask)

.referenzen .grid-content a {
  pointer-events: auto;
}

.referenzen .grid-content:hover {
  opacity: 1;
  transform: translate(-50%,-50%);
  transition: 1s all ease;
}

.referenzen .grid-image .image-overlay {
  z-index: 0 !important;
  display: none !important;
}

and this to your child-theme functions.php:
(and because this should only affect portfolio grids that are set to lightbox, here is the selector with grid-links-lightbox class.)

function open_non_lightbox_links_in_portfolio_grid(){
?>
<script type = "text/javascript">
window.addEventListener("DOMContentLoaded", function () { 
  (function($){
    $('.grid-links-lightbox .grid-entry  a:not([href^="#"])').on('click', function(e){
        e.preventDefault();
        var externalLink = $(this).attr('href');
        window.open(externalLink, '_blank');
    });
  })(jQuery);
});
</script>
<?php
}
add_action( 'wp_footer', 'open_non_lightbox_links_in_portfolio_grid' );

you see what the code does?
you have set the portfolio grid to open all links in a light box.
But your e-mail or links to external Links are not from the type: href=”#…” – the attribute selector above excludes these links to popups – and only prevents the function of the lightbox script where the links do not start with a hash (#).

PS: if you like to open those links not in an additonal window replace _blank with _self

this is always a problem – to have a clickable link over a clickable background-image.
and especially for that case – because the hover effect is correlatet to the link of the background.
If you now hover a link inside that container – the hover focus is lost.

you can see what i mean if you use:

.referenzen .grid-content a {
  pointer-events: auto;
}

but your link there is not clickable anyway – because
we have here multiple issues – you declared the links inside to lightbox links ( inline popup ) so – both links in your last container are no popup – external page links ( and if lightbox – they had to be iframe popups)

if you do not like to strip the excerpts try in child-theme functions.php :

function my_avf_masonry_loop_entry_content($loop_excerpt, $entry) {
  $loop_excerpt = $entry->post_excerpt;
  return $loop_excerpt;
}
add_filter('avf_masonry_loop_entry_content', 'my_avf_masonry_loop_entry_content', 10, 2);

but i do not know if the “wordpress” excerpts are included by that. The Enfold Excerpts are influenced by that snippet

Edit : tested – but it does not work anymore – i had to inspect the loop

Also tausche nur den eingesetzten css Code im Quick Css aus gegen:
(ändere je nach Bedarf diese Grenze 989px aus unter der das gelten soll)

/**** Farbdefinitionen überall ****/
#top .av-masonry.description-below .av-inner-masonry-content,
#top .av-masonry.description-below .av-inner-masonry-content .avia-arrow {
  background-color: #cde5a5;
}

/****** hover Verhalten abschalten für den responsiven Fall ********/
/****** bei Querformat iPad Pro 12,9inch = 1367px / bei iPad Pro 11inch = 1195px ********/
/****** bei Querformat iPad  10,2inch = 1081px / etc. pp ********/

@media only screen and (max-width: 989px) {
  .responsive #top .av-masonry.description-below .av-inner-masonry-content {
    position: relative !important;
    top: 100%;
    opacity: 1 !important;
    animation: none !important;
    transform: none !important;
  }

  .responsive #top .av-masonry.description-below .av-inner-masonry {
    overflow: visible;
  }

  .responsive #top .av-masonry.description-below a.av-masonry-entry {
    margin-bottom: 60px !important;
  }

  .responsive #top .av-masonry.description-below .av-inner-masonry-content {
    padding: 5px 10px;
    text-align: center;
    min-height: 65px
  }

  .responsive #top .av-masonry.description-below .av-inner-masonry-content .av-masonry-entry-title {
    position: absolute;
    top: 50%;
    left: 50%;
    transform: translate(-50% , -50%);
    padding: 0 !important;
    margin: 0 !important;
    width: 100%;
    font-size: 18px !important;
  }
}

siehe hier mal : https://webers-testseite.de/gallery/
PS: die Seite nutzte ich schon einmal als testseite, daher liegt da noch ein anderer hoverstyle zu grunde. Farben etc. – ist aber für dein hover state Aspect nicht relevant.

But – please, this only replaces the behaviour on mobile devices. This happens when the descriptions are permanently displayed because the hover effect cannot be effective. So that these overlays do not cover a main part of the image, they are moved here below the images.

If you also want to use it on the desktop with small screen widths, we have to remove the class avia_mobile from the code and put the whole thing in a media query, e.g. only up to 767px.

i can not see the custom class – did you save it after entering the class?

when entering the code without that custom class on my developer tools to test if it works
(Emulation is ipad)