Hi,

Found several typos in original English:

“Some SEO plugins need to process shortcodes when bulding the header” -> should be ‘building’
“protocoll” -> “protocol”
“Load google fonts in footer”-> Google
“Only use if you know what you are doing ;)” -> ;-)
“The Font heading allows you to use a wide range of fonts for your headings. Uplooad your own fonts, use websave fonts (faster rendering) or Google webkit fonts (more unique).” -> Upload
“Show Thumnails and display post title by tooltip” -> Thumbnails
“Show Blog Sidebar on Archiv Pages” -> Archive
“Disable advance layout builder preview in backend” -> Advanced Layout Builder
“Hide badge and string completly on every page” -> completely
“instagram” -> Instagram (several places)
“Linkedin” -> LinkedIn

Regards,
Roger
PS Working hard on completing Dutch translation

• This reply was modified 5 years, 11 months ago by EZWebdesign.

@webvriend,

I didn’t realise the Responsive images came from core as well! Wow OK this is going to be the final tick in a box for Enfold for me. If we get Lazy load support as well then the only way to further improve it performance wise will be to reduce the main framework.

I’ll be testing autoptimize when I get the chance to reduce the size of the merged files.

Looks like the Devs at Enfold have some work to do! I will still compress all images before uploading them. It helps keep the server and database clean. But When the update lands I will need to regenerate thumbnails for all of my websites so I can enable the feature.

@webvriend @gunter
Not sure if you have seen but WordPress core team are planning to launch Lazy loading of images as standard in WordPress Core. Lazy load is being added to all major browsers as a html solution rather than relying on Javascript. I’d imagine that for enfold to add responsive images, that the Enfold team will need to wait until after the new lazy loading attributes are added to the core, otherwise the new responsive image coding may not be compatible with lazy load.

@gunter – Just so you are aware, I currently use a plugin to stop enfold from generating all of the image sizes due to node limitations on my server. I.e. The maximum number of files allowed is about 250,000. Split over several websites I would need to massively increase the number of server packages I currently use to accomodate all of the Enfold sites I run if I had to allow every single enfold image size to generate on each site. I am not sure how you intend on adding responsive image sizes to Enfold but I may have to regenerate all images on every site in order for this to work.

@webvriend have you tried using Jetpack’s site accelerator? I believe that it automatically picks the best fit for each image size? assuming you have allowed all thumbnails to generate? I have experienced the odd issue with this where it picks the wrong image size for the space available.

Hello,

I know this is an old thread but it showed up on Google when I searched for the same possibility.
I figured to make it work : display a 2:3 ratio image to Pinterest share pins.

First, you need to create a custom size with 2:3 ratio, here I took 600×900 :

add_image_size( 'pinterest-size', 600, 900, true );
add_filter( 'image_size_names_choose', 'custom_pinterest_size' );
function custom_pinterest_size( $sizes ) {
    return array_merge( $sizes, array(
        'pinterest-size' => __( 'Ratio 2:3' ),
    ) );
}

Then, you can edit the pinterest URL pattern with avia_add_social_share_link_arguments :

add_filter('avia_social_share_link_arguments', 'avia_add_social_share_link_arguments', 10, 1);
function avia_add_social_share_link_arguments($args)
{
	if(is_single() && get_the_ID()){
		$args['pinterest'] = array("encode"=>true, "encode_urls"=>true, "pattern" => "https://pinterest.com/pin/create/button/?url=[permalink]&description=[title]&media=".get_the_post_thumbnail_url(get_the_ID(), 'pinterest-size'), 'label' => __("Share on Pinterest",'avia_framework'));
	}
	return $args;
}

And that’s it !
Hope it will help some other who get to this thread from Google with the same issue.

just for info: we do not need the shortcode

and because on the most cases it makes no sence on showing the featured image on a post or portfolio created with advanced layout builder – we can use the meta box setting of showing or not showing the featured image.

add_filter('avf_template_builder_content', 'avf_template_builder_content_postimage_mod', 10, 1);
function avf_template_builder_content_postimage_mod($content = "")
{
  if(
  	is_singular('post') && ( '1' != get_post_meta( get_the_ID(), '_avia_hide_featured_image', true ) ) 
  	||  is_singular('portfolio') &&  ( '1' != get_post_meta( get_the_ID(), '_avia_hide_featured_image', true ) ) 
    ) 
  {
    $featuredImage = get_the_post_thumbnail( $the_id, 'entry_with_sidebar' );
    $content = $featuredImage . $content ;
  }
  return $content;
}

Hello Victoria
thank you for your reply. If I add “Griglia di Prodotti” as suggested I got the list of all the products available in the shop. Maybe it was me who misguided you to the wrong solution because I was not clear. Anyway, I need instead the Image gallery and zoom options for the single product, that is the possibility to zoom in the image of the product in the product page, and the thumbnails of other images (related to the same product) also in the product page, under the main image.

Looking forward to your answer.
Thank you
Alessandra

• This reply was modified 5 years, 11 months ago by aledelpu.

or – you determine a different image-size as source for the lightbox image
for masonry galleries – this to child-theme functions.php:

function avia_change_masonry_thumbnail_link($size){
  return "full";
}
add_filter('avf_avia_builder_masonry_lightbox_img_size', 'avia_change_masonry_thumbnail_link', 10, 1);

then it will take the full image size ( original uploaded Image ) for it

btw: for different images ( image lightbox or gallery etc.) there are different filters to use
avf_avia_builder_gallery_image_link or
avf_avia_builder_helper_lightbox_size

PPS: for your mobile rendering of the image : no solution yet.