Hey Guenter,

A first response:

The basic implementation for responsive in enfold is that you have a setting with no media query (description is desktop – no media query) either in css files or set in options and then media queries that override the desktop setting.

I think this is also a historical reason because responsive was added later.

Changing this will certainly break many sites.

But I agree – there is missing an option with a media query for large screens only (wider than 990px).

This would allow:

• set a custom default value for all sizes (and override theme setting)
• set a custom value for each of the 4 devices independently, if not set the custom default value for all sizes or theme default is used

I will think about it a little more.

This can also be used for font sizes and other responsive settings

Best regards,
Günter

Hi,

Thanks for providing the code.
I added it to core for 5.0.2.

Replace enfold\framework\php\class-media.php:

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_0_1/framework/class-media.php

I had to replace

$query->set('orderby', 'meta_value_num'); 

with

$query->set('orderby', 'ID'); 

and

 remove $query->set('meta_key', 'post_attachments_id');

Best regards,
Günter

Hi Tim,

Please try to update enfold\config-woocommerce\config.php with the content of

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_0/config-woocommerce/config.php

This should now show responsive images or the “large” image (if theme option Responsive Images For Lightbox is disabled). You can change the default lightbox image size with filter avf_avia_builder_helper_lightbox_size.

@guenni007

If you set ratio to > 1 @2x is added.

If theme option Responsive Images For Lightbox is disabled I get “Image could not be loaded” (because I do not have such a file uploaded), with option enabled I get the correct image responsive image (without @2x).

Best regards,
Günter

Hi,

Sorry for that.

A modified fix is integrated in the latest release 5.0 published yesterday.
Can you check with this version if the problem is fixed please.

Best regards,
Günter

Hi,

@thinkjarvis

Thank you for bringing this up.

I checked the font behaviour of the “Special Heading” element with 4.8.3 (a version prior the post css file changes).

Setting Heading Font Sizes – Font Size (Default) to e.g. 50px, responsive Font sizes to “Use default”.

The 50px are used for all devices (because added inline in a style tag).
There is a media query in heading.css:

@media only screen and (max-width: 767px) {
	#top #wrap_all .av-inherit-size .av-special-heading-tag{ font-size: 0.8em; }
}

And this is what I missed to implement when switching to post css file implementation.

And the only difference I can see.

Would adding this help you ?

And I’m also thinking about extending the selectable font sizes with flexible units also for responsive:

vw
em
rem

Maybe an option for pro users to replace the dropdown with input boxes ?

Best regards,
Günter

Hey!

For your information:

This problem is fixed in oncoming version 5.0.

You also have a new option “Deeplink String” (Advanced Tab -> Developer Settings) where you can define a custom lnk hash for the tab.

Cheers!
Günter

Hi,

In addition to @Guenni007:

If you only modify class-avia-masonry.php you can copy the original file to “$template_url.’/shortcodes/'” and your copy will be loaded before the original file preventing loading this.

There is no need for a directory structure.

Only in case you need control which modified files in your child theme must be loaded before other files you can create a directory structure but must add this structure e.g.

add_filter('avia_load_shortcodes', 'avia_include_shortcode_template', 15, 1);
function avia_include_shortcode_template($paths)
{
  $template_url = get_stylesheet_directory();
      array_unshift($paths, $template_url.'/shortcodes_1/', $template_url.'/shortcodes_2/' );

  return $paths;
}

and then file inside shortcodes_1 are loaded before files in shortcodes_2.

Best regards,
Günter

Hi,

Thanks for reporting this.

Fix will be included in Enfold 5.0.

If you need a temporary fix let us know and we can provide it.

Best regards,
Günter

Hi,

Here you can find a rough overview of upcoming releases:

https://kriesi.at/support/topic/enfold-upcoming-fixes/

Best regards,
Günter

Hi,

Thank you for reporting this – and very sorry for the problems.

Icon Grid problem should be solved – please check your staging site. Was caused by a wrong selector to apply the selected font size (resulted in a wrong padding).

Widget problem also solved for ALB Widget area.

Already added for next update 4.9.2.2 which is planned in the next days.

If you do not want to wait you can copy the 2 modified files (do not forget to make backups of the original files for a fallback):

enfold\config-templatebuilder\avia-shortcodes\icongrid\icongrid.php
enfold\config-templatebuilder\avia-shortcodes\widgetarea\widgetarea.php

And you need to save theme options to invalidate the post css files and clear server and browser cache.

Best regards,
Günter

Hi,

No idea why the script is reported as a security alert.

The only thing you can try is if you do not need the GDPR stuff to remove our script with the filter and enqueue your own or modify the core file and only use the code within

if( allow_continue )

Maybe there is an option to allow fonts.googleapis.com as a secure link ?

Best regards,
Günter

Hi,

Thanks for your feedback.

Glad we could help you. Enjoy the theme and have a great day.

Feel free to come back whenever you need assistance.

Best regards,
Günter

Hi,

Having a look in your backend:

PHP is very outdated with 5.6.40. You should upgrade to minimum 7.4.xx (or 8.0.xxx) – also for security reasons.
Enfold is also not up to date – we have 4.9.2.1 out since a few weeks.

Also depending on your hoster it could be, that he is doing some caching. You should check this and if yes, maybe he can provide you a staging server without this caching for testing.
WPML has integrated the translation management in core lately (it was a seperate plugin before) – therefore they encourage to use “Translate” and not “Duplicate”.

This also works very well with our Advanced Layout Builder.

We have fixed 2 minor WPML bugs in next Enfold 4.9.2.2 – so if update to 4.9.2.1 does not help we can give you a pre release of 4.9.2.2 to test.

Best regards,
Günter

Hi Tim,

I’ve not really digged into schema.org.

But having a look at https://schema.org/VideoObject and the examples at the bottom of the page the only idea I have would be to add a meta tag like:

<meta itemprop="contentUrl" content="link_to_video" />

right after the opening div of the video element.

Could you check if this helps please?

Best regards,
Günter

Hey Caiser_Souze,

Sorry for the problems.

Please update to the latest version 4.9.2.1. This should fix the problems.

Best regards,
Günter