but this will be a function that will depend on scroll and resize. Be carfully with it -because this mostly goes to bad performance.

$(window).on(‘resize scroll’, function() {
//Code here
});

you can see here a littel code-pen demo: https://codepen.io/BoyWithSilverWings/pen/MJgQqR

you see that there is a function defined isInViewport

• This reply was modified 6 years, 10 months ago by Guenni007.

you can use a filter for it – or use a header-widget but
without seeing your site and logo it is hard to give exact settings for you.

Sorry but this is more or less for the developers :

the more I think about the topic I come to the conclusion that Kriesi also confuses the nomenclature here.
Fullscreen Slider has the class: avia_sc_slider_fullscreen –
the fullwidth Slider has the class: avia_sc_slider_full.
Although it writes in the code ( dont display if a fullscreen slider ) clear fullscreen slider in functions.php above, the code only checks against avia_sc_slider_full

and i definitly think that this is something which should be seen by Günter – because i believe it should be implemented too in the next update !
It makes sense to also hamper sidenavigation on fullscreen sliders on default

_________________
Something to the developers
Edit: to my opinion on that code: avia_post_nav
the code is not totaly correct with the brackets too in the if clause

		//dont display if a fullscreen slider is available since they overlap 
		if((class_exists('avia_sc_layerslider') && !empty(avia_sc_layerslider::$slide_count)) || 
			class_exists('avia_sc_slider_full') && !empty(avia_sc_slider_full::$slide_count) ) $settings['is_fullwidth'] = true;

as far as i understood the code the post-nav should also be displayed if only one slide is present – only if there are more than one slide the post-nav should be hampered.
But it does not work even with original code on full-width sliders.

this seems to be the right bracket story including fullscreen-slider check – but it does not work for count too:

//dont display if a fullscreen slider is available since they overlap 
if(
	( class_exists('avia_sc_layerslider') 	&& !empty(avia_sc_layerslider::$slide_count) ) || 
	( class_exists('avia_sc_slider_full') 		&& !empty(avia_sc_slider_full::$slide_count) ) || 
	( class_exists('avia_sc_slider_fullscreen') && !empty(avia_sc_slider_fullscreen::$slide_count) ) 

	) $settings['is_fullwidth'] = true;

So my dear Dev Günter with the same first name – here you have to look over it.
or does a single (full-width or full-screen) slide has a count too?

• This reply was modified 6 years, 10 months ago by Guenni007.

By the way – i guess that role attribut are only warnings – so ignore them – because on wai aria (Accessible Rich Internet Applications) usage is good standard. And for my opinion it is more important to have these roles in a html document than to fullfill w3c validity.

ich denke hier an Board und auf etlichen anderen Boards ist das Du üblich.

Also bitte gern geschehen.

isn’t it this the normal behavior (see line 526 of functions-enfold.php). the fullscreen-slider detection hampers the prev/next navigation.
As far as i know it is on the contrary; you have to activate it explicitly to suppress the full-slider detection via functions.php of your child-theme.
this code is to have the prev/next navigation allthough there is a full-slider

So maybe you check if you got such an entry on your functions.php

add_filter('avia_post_nav_settings','avia_remove_fullwidth_slider_check', 10, 1);
function avia_remove_fullwidth_slider_check($settings)
{
$settings['is_fullwidth'] = false;
return $settings;
}

Just please do not make the mistake of making the validity of the law dependent on the place of access to your site. You are obliged to protect the data of citizens from other countries too. The place of jurisdiction depends on your side. In addition, all those who have business relations with the EU area and its citizens must adhere to it.

And more important – the most cookie consent plugins do not hamper the tracking before opt-in.
I got Borlabs Cookie – and i think it is one of a few that do exactly this. The whole site is blocked without defined pages like Privacy Policy and Imprint.

i would prefer the last method to make another “social button” and style it a different way.

by the way i’m a participant as you are so i do not see private content.

it depends on your hoster – my hosting works fine with 640 but the lines:

# secure htaccess-file
<files ~ "^.*\.([Hh][Tt][Aa])">
order allow,deny
deny from all
satisfy all
</files>

are a bit of security for that file.

for some of my customers i have to set the file to 644 too. – sorry

https://tools.pingdom.com/#!/dNdVKn/https://fotowalther.ch/
https://gtmetrix.com/reports/fotowalther.ch/0S0UKllk

but if you take instead a server in Europe see:
https://gtmetrix.com/reports/fotowalther.ch/euHFHSZv 1,9 sec

Seems to be ok now. don’t let yourself become a slave to these testing-sites, they just give good hints where to hook.
The pictures are often criticized there to optimize, but strangely only your logo is too large. Why don’t you take a jpg instead of png which is 1/5th the size.
The other images have only a 4% reducing amount – it comes from our little calculation to the given screenheight.

this works on four of my installations: https://de.wordpress.org/plugins/wp-mail-smtp/

aha – you did not mention that it is concerning to an open graph issue.
i think this is not a matter of the embed code but a matter of missing og infos on Enfold pages.
On Enfold there are without plugins no og: entries in the head area of the page. A lot of seo tools will add them (including facebook et.al. entries) – or you can do it manual via functions.php.

content cards i think uses these entries to show a preview of your page.
for a preview image the <meta property=”og:image” … is taken

you can add these infos via functions.php of your child theme:
if you have a seo tool look to your head section what is already placed there and add only the missing infos
on yeost seo f.e. the image is missing

add_action( 'wp_head',  'add_og_site_information', 10);
function add_og_site_information() {
	?>
		<meta property="og:locale" content="de_DE" />
		<meta property="og:type" content="website" />
		<meta property="og:title" content="Guenter Weber - Werbung" />
		<meta property="og:description" content="Guenter Weber, digitale Dienstleistungen" />
		<meta property="og:url" content="http://guenterweber.com/" />
		<meta property="og:site_name" content="Guenter Weber - Werbung" />
		<meta property="og:image" content="https://guenterweber.com/wp-content/uploads/vorschaubild.jpg" />
	<?php
}

see here on the right side of the page a content card of an enfold page:
https://webers-testseite.de/link-to-website-with-live-preview-on-hovering/

i can not confirm to that – your page loads on my end fast enough.
but i have a 200mbit connection

but see here your results: https://gtmetrix.com/reports/fotowalther.ch/L1YaUTiT

it seems that you have no gzip compression enabled ! (this is relevant for performance)
and no leverage browser caching is defined and no expires header is set.

i do always activate it via the htaccess file ( but it depends on your server) but commonly they serve as an apache server.
this is a hidden file ( .htaccess) – but a lot of ftp clients can make them visible on default.
you can download the file ( if you have f.e. a different permalink set – there will be one) via ftp – rename it to htaccess.txt and edit it with a good text editor ( f.e. : sublime text for mac or notepad++ for Windows)

on default there will be something like this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

this existing entries have to be be untouched and depends on your settings you made in the dashboard.
Most of the caching tools put in a lot of entries here.

My settings for example are in front of that existing entries: ( means in front of # BEGIN WordPress):

# Secure your wp-config
# Disallow access to important files
<FilesMatch "(^\.|wp-config\.php|xmlrpc\.php|(?<!robots)\.txt|(liesmich|readme)\.*)">
   Require all denied
</FilesMatch>

# secure htaccess-file
<files ~ "^.*\.([Hh][Tt][Aa])">
order allow,deny
deny from all
satisfy all
</files>

# Keep-Alive
<ifModule mod_headers.c>
   Header set Connection keep-alive
</ifModule>
 

# Gzip
<IfModule mod_mime.c>
    AddType application/javascript          js
    AddType application/vnd.ms-fontobject   eot
    AddType application/x-font-ttf          ttf ttc
    AddType font/opentype                   otf
    AddType application/x-font-woff         woff
    AddType application/x-woff              woff
    AddType image/svg+xml                   svg svgz 
    AddEncoding gzip                        svgz
</Ifmodule>
 

# GZip Kompression
<IfModule mod_gzip.c>
 mod_gzip_on       Yes
 mod_gzip_dechunk  Yes
 mod_gzip_item_include file      \.(html?|txt|css|js|svg|php|pl)$
 mod_gzip_item_include handler   ^cgi-script$
 mod_gzip_item_include mime      ^text/.*
 mod_gzip_item_include mime      ^application/x-javascript.*
 mod_gzip_item_exclude mime      ^image/.*
 mod_gzip_item_exclude rspheader ^Content-Encoding:.*gzip.*
</IfModule>

 
# Browsercache
<IfModule mod_expires.c>
 ExpiresActive On
 ExpiresDefault "access plus 1 month"
 ExpiresByType text/css "access plus 1 month"
 ExpiresByType text/javascript "access plus 1 month"
 ExpiresByType text/html "access plus 1 month"
 ExpiresByType application/javascript "access plus 1 month"
 ExpiresByType application/x-javascript "access plus 1 month"
 ExpiresByType application/x-font-ttf "access plus 1 month"
 ExpiresByType application/x-font-woff "access plus 1 month"
 ExpiresByType application/x-woff "access plus 1 month"
 ExpiresByType application/xhtml-xml "access plus 600 seconds"
 ExpiresByType application/pdf "access 1 month"
 ExpiresByType image/gif "access plus 1 month"
 ExpiresByType image/jpg "access plus 1 month"
 ExpiresByType image/jpeg "access plus 1 month"
 ExpiresByType image/svg+xml "access plus 1 year"
 ExpiresByType image/svg "access plus 1 year“
 ExpiresByType image/png "access plus 1 month"
 ExpiresByType image/x-icon "access plus 1 month"
</IfModule>

 
# Deflate by FileType
<IfModule mod_deflate.c>
 AddOutputFilterByType DEFLATE text/plain
 AddOutputFilterByType DEFLATE text/html
 AddOutputFilterByType DEFLATE text/xml
 AddOutputFilterByType DEFLATE text/css
 AddOutputFilterByType DEFLATE text/javascript
 AddOutputFilterByType DEFLATE image/svg+xml
 AddOutputFilterByType DEFLATE application/javascript
 AddOutputFilterByType DEFLATE application/xml
 AddOutputFilterByType DEFLATE application/xhtml+xml
 AddOutputFilterByType DEFLATE application/rss+xml
 AddOutputFilterByType DEFLATE application/atom_xml
 AddOutputFilterByType DEFLATE application/x-woff
 AddOutputFilterByType DEFLATE application/x-font-ttf
 AddOutputFilterByType DEFLATE application/x-font-woff
 AddOutputFilterByType DEFLATE application/javascript
 AddOutputFilterByType DEFLATE application/x-javascript
 AddOutputFilterByType DEFLATE application/x-shockwave-flash
</IfModule>
 
# ETag
Header unset ETag
FileETag None

you see here both the older gzip and the more modern mod_deflate module.
on mod_expires you can set different time settings – optimized for your website.

After uploading this htaccess.txt file – rename the existing .htaccess to htaccess.bak ( to have a fallback)
then rename the new file to .htaccess(be carefull to set the dot before the file) – maybe it is a good advice to set the file permissions to 640.

in addition to that – that is the right way.
Important : no space between tel: and number
By the way the input field of Enfold phonenumber accepts html. (as copyright input field too)
And you can set as link your correct number with your contrycode etc

<a href="tel:+492289768293"> get in touch etc. pp anything you like</a>

if you let the background-image determine the height of the color-section (yes this is possible) you will have troubles on small screens to have all content in that color-section. ( that is the reason why the content normaly determines the section height)

see here – i gave to the color section a custom-class: responsive-container

and did this to quick css:

.responsive-container {
    background-size: contain;
    padding-top: 56.25vw;
    width: 100vw;
    height: 56.25vw !important;
}
.responsive #top #wrap_all .responsive-container .container {
    margin-top: -56.25vw
}

see result here – and see for smaller screens what i mean with troubles: https://webers-testseite.de/responsive-colorsection/

so better is to have background-images which could be cropped or to have interesting gradients

ja und nimm die Original Bilder: Slideshow Image and Video Size : no scaling

wenn du möchtest, dass die Bilder oben unten nicht über den Screen gehen. kann man das erzwingen:
gib der full-width slideshow eine Custom Class. ich habe das mal mit zweien deiner Bilder gemacht, und der Slideshow die klasse: vollehoehe
gegeben.

dann habe ich ins quick css folgendes eingegeben:

.vollehoehe img {
    max-height: calc(100vh - 170px);
}

die minus 170px sind dem Header-bereich geschuldet. Da kannst du noch ein wenig dran drehen.
https://webers-testseite.de/slide-show/

wenn du es gesehen hast – nehme ich die Bilder wieder raus.

Wenn du es nur auf der startseite hast kannst du es auch so selectieren:

.home .avia-slideshow img {
    max-height: calc(100vh - 170px);
}