Hi,

Thank you for the feedback and glad we could help you.

Feel free to come back when you need further assistance and enjoy the theme.
Have a great day.

Best regards,
Günter

Hi,

@royaltask

Option Default Cookie Behaviour: User must accept and must opt in, only essential cookies selected

Und dann gibt es: button action: Accept all cookies and services, dismiss notification

Siehe auch https://kriesi.at/support/topic/enfold-cookie-consent-like-bor-labs-possible-better-results/

Best regards,
Günter

Hi,

Thank you for your feedback. I forwarded it to WPML so they can continue to investigate.

Enjoy the theme and have a great day.

Feel free to come back if you need further assistance.

Best regards,
Günter

Hi,

Thank you for coming back.

I’ve been in contact with WPML – they are having an eye on it.

There is a WPML problem with Avia Builder and special characters (like german Umlaute ä,ü,.. but likely also those in other languages).

It would be helpful to find out, which ALB element causes the problem. So the only way would be to make a copy of the page and then remove one element after the other and check if the translations still break (or the other way add elements to an empty page with the same setup one by one).

Best regards,
Günter

Hi,

@THP

Checked it. For me it works.

But it depends on your settings.

Background images do not support scrset as the img tag – only for resolution (https://developer.mozilla.org/en-US/docs/Web/CSS/image-set)

If you select Image size behaviour to “no stretch” you get img tags and you must select an image size that has responsive thumbs (check option “Responsive Images Thumbnails Overview:”).

Best regards,
Günter

Hi,

Thank you for using Enfold.

Up to now we did not get any bug reports with translation editor and Enfold.
WPML has a compatibility team to integrate Enfold and also does a lot to keep everything running smoothly. And we also are in contact with them.

For your special case – this seems to be related to WPML and not to Enfold.

Did you already open a support ticket at WPML?

Best regards,
Günter

Hi,

Thank you for coming back and the credentials.

I setup a staging site on my dev server (with a page as footer) – using the 5 basic WPML plugins (Multilingual CMS, Translation Management, String Translation, Media, WC Multilingual) and WooCommerce. I cannot reproduce the problem. I can add a product to cart in both languages without the popup, this appears only when I switch the languages.

Also deactivating all other plugins on your staging server does not produce the error any longer.

It is correct, that $post->ID in function wcml_language_switch_dialog() points to the translated footer page ID.

It seems, that one of the other plugins hooks into the get_posts() query for the footer page and modifies the global $post variable.

The only way to find out is to deactivate all plugins (except the basic ones mentioned above) and then reactivate one by one until the problem occurs again.

Best regards,
Günter

Hi Nico,

@vdlpwp

Thanks for your research. This sounds like a problem we also had with merged css and js files and this was related to a known but unfixed WP bug:

https://github.com/pantheon-systems/wp-redis/issues/221
https://core.trac.wordpress.org/ticket/31245#comment:57

I added a fix for the next release.

If you have a staging site and want to test a temp. fix:

In enfold\framework\php\auto-updates\auto-updates.php line 729:

update_option( 'avia_envato_keys', $theme_keys );

After that line add:

wp_cache_delete( 'alloptions', 'options' );

That should force to save the updated options to database.

Best regards,
Günter

Hi!

Sorry for the problems you have.

It is caused by WP 5.5 having changed the way it treats pagination and this breaks our theme logic. If you switch back to 5.4.2 everything is working as expected.

We are working on a solution.

Cheers!
Günter

Hi!

Thank you for reporting this.

I forgot to remove the tab after finishing the element – at the moment it is not needed. Will be part of the next release.

Best regards,
Günter

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