Hi Roger,

Thank you for helping to improve Enfold.

I merged your pull into core, fixed the typos 2 + 3 – already in core.

I made a sync including the latest updates and all language files and uploaded it to github https://github.com/KriesiMedia/enfold-language-files.

For your dutch there are now 2 untranslated strings remaining – probably the fixes I made.

Concering the select box: The content is coming from a standard WP function call – should actually be translated by WP (?). But I will check when I have a spare time.

Best regards,
Günter

Hi Rob,

Exactly. Jetpack is overriding Enfold. ( and probably also WP, because it handles lazy loading for its own with js which will get in conflict with the html attribute).

If you have time you can keep jetpack lazy loading disabled and enable Enfold lazy loading for each element and check, if a page works as expected – would mean that at least modern browsers can take advantage of this feature – without any overhead of javascript. Older browsers simply ignore this attribute.

Best regards,
Günter

Hi,

Thank you for giving us access to your dev server.

Finally I could locate the problem: $params was not an array but a query string.

I added in line 1628 (enfold\config-woocommerce\config.php):

$params = wp_parse_args( $params );

This should fix the problem.

Best regards,
Günter

Hey!

@Guenni007

Thanks for sharing the fix.

Will be added to next release – should come in the next days (as WP 5.5 is close to release).

Best regards,
Günter

Hi,

Ich habe einmal eine “Clean functions.php” hochgespielt (functions_clean.php). Mit dieser funktiniert V2 und (nach einigen clear browser cache) auch V3. Habe für beide ein autoresponder Mail erhalten. Du solltest in deinen somit auch einige erhalten haben – Testseite siehe unten.

Hab es auch als nicht angemeldeter Benutzer in Chrome in einem normalen Fenster getestet.

Ich habe wieder auf die alte functions.php umgestellt.

Irgend ein code in Deiner functions.php dürfte somit etwas stören. Wäre interessant, das zu eruieren. Vielleicht kann man dann einen Fix einbauen auch für andere User, die Probleme haben.

Best regards,
Günter

Hi,

WP creates the srcset from images with the same aspect ratio ( +/- 1 px ) as the image you are displaying.

This means if the displayed image has e.g. 700px * 700px thumbs with a aspect ratio of 1:1 are considered responsive for scrset.

If your displayed image e.g. has 1280 * 720 ( 16 : 9 ) and you do not have thumbs with 16 : 9 the image does not get any scrset.

You find a list of thumbs in Enfold Options page -> Performance -> Responsive Images -> Image Thumbnails Info.

If you need responsive images for 16 : 9 you will need to add additional image thumb sizes for 16:9.

Best regards,
Günter

Hi,

The reason why the images are not visible is a CSS rule:

img[data-lazyloaded] {
    opacity: 0;
}

located in a script from litespeed.

WP creates the srcset from images with the same aspect ratio ( +/- 1 px ). Do you have thumbs that have the same aspect ratio as the original image?
You find a list of thumbs in Enfold Options page -> Performance -> Responsive Images -> Image Thumbnails Info.

Best regards,
Günter

Hi,

Lösung wird ziemlich sicher Teil der nächsten Release werden.

Einen schönen Tag noch.

Best regards,
Günter

Hi,

@THP

Thanks, yes, I missed it. Will be part of next update.

If you want to update, you can replace

enfold\framework\php\function-set-avia-frontend.php

with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_7_6_1/function-set-avia-frontend.php

Best regards,
Günter

Hey Guenter,

Not sure if this is what you meant, but I extendend the lightbox script that when no title attribute exists (which currently leads to an empty title string in lightbox) it searches for the alt attribute and displays it instead.

And for the fixed size I also copy the alt attribute to the a tag.

Does that make sense?

To check use 4.7.6.1 and replace

enfold/js/avia-snippet-lightbox.js and
enfold/config-templatebuilder/avia-shortcodes/av-helper-masonry.php

with:

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_7_6_1/lightbox_fix/avia-snippet-lightbox.js
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_7_6_1/lightbox_fix/av-helper-masonry.php

Best regards,
Günter

Hi,

Thanks for this info. I’m pretty sure that was missing also in previous versions.

I merged it for the next update.

Have a nice day.

Best regards,
Günter

Hi,

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

Feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

@thp

Our latest beta version (4.7.5.1-beta-3) includes support for all ALB elements. If you are interested in testing, please open an own thread and we can give you a link to it in private content when it is ready.

Thanks for pointing at lazy loading. I added this to our dev repo and we will adress it asap.

Best regards,
Günter

Hi,

@guenni007

I agree – it is in the duty of the website owner to add a GDPR complient content to the Maintenance mode page.

As you say – you can create a simple page …..

The only thing that Enfold can do is not to load scripts like Google fonts and other services Enfold offers on that page when maintenance mode is enabled.

But that’s it.

Best regards,
Günter

Hi,

@VariablerEsel

Danke für diese Info.

Ich schliesse dieses Topic. Sollten weitere Fragen auftreten, bitte ein neues Topic anlegen.
Einen schönen Tag noch.

Best regards,
Günter