It depends a bit on what kind of header you have and what you want to achieve.
Is it a fixed header on desktop view? Where is your navigation etc.?
the header_meta should stay fixed in mobile view – and not scroll away…

or – have a look into the docu : https://kriesi.at/documentation/enfold/icon/#download-fontello-or-flaticon-icons-included-in-enfold-demos

is wp-block-heading a class ? Where’s the dot before?
next – you only want to change h1 headings with that custom class and all h2 ?

Ich wäre davon ausgegangen, dass nur Admins dieses Recht besitzen!
Denn das hier ist die Ansicht, die ein Redakteur zu sehen bekommt:

_________

I would have assumed that only admins have this right!
Everything else makes no sense either.
This is the view that an editor gets to see:

if you got a css code error on quick css ( a missing closing bracket (often forgotten on media querries) , comma instead of semi-colon (or vice versa) , etc pp) the rest of your css could be ignored.
this enfold setting of container max-width is added after the quick css settings – so it will go back to the standard container width of 1010px (see: grid.css ) .

/* Base sizes */
.container .av-content-full.units  {
	width: 100%
}
.container .av-content-small.units {
	width: 73%
}
.boxed#top, .html_boxed.html_header_sticky #header{
	width: 1010px;
}
.container{
	max-width: 1010px;
}

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 2 years, 5 months 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