Hi,

@tholtmann

User must accept cookies – then the cart works.

We will add an option where essential cookies will work even if user does not accept cookies. If this is legal – it is up to you to decide.

Please have a look here for more info: https://kriesi.at/support/topic/enfold-4-7-1-cookie-consent-problem-with-woocommerce-cart-still-exists-%f0%9f%98%b1/#post-1176332

Best regards,
Günter

Hi,

Interesting – in buttons we have

<a>

links.

I think I found a better solution – replace 642 with:

					var a = document.createElement('a');
					a.href = url;
					a.target = '_blank';
					a.rel = 'noopener noreferrer';
					a.click();
					return false;

Best regards,
Günter

Hi,

Glad we could help you.

Enjoy the theme and feel free to come back if you need further assistance.

Best regards,
Günter

Hi,

For your information:

We will add an option for the next release where you can disable the accordions in the ALB modal popups.

Best regards,
Günter

Hi,

We will add an option “Accept essential cookies on pageload, user must opt in for other cookies”.

This will allow essential cookies by default (like WC cart, enfold cookies) and user must opt in for other services.

Should be in 4.7.3.

Best regards,
Günter

Hi,

It is clearly explained in the docu:

Option User must accept and must opt in, only essential cookies selected

If a user does not address the settings and only accepts cookies the site will have all basic functions excluding external services – this is an intuitive behaviour and what a user would expect.

As everything is blocked until user clicks the accept button this is GDPR compliant (there are discussions, but many people interpret the rules that a user cannot refuse essential website cookies).To allow website owners to be on the safe side using add_theme_support(‘avia_privacy_basic_cookies_unchecked’); will also uncheck the 2 toggles.

And also:

Only the 2 toggles “permanent hiding message bar” and “enable essential cookies” selected, all other unchecked, services blocked until user accepts settings.

There is no need to accept other cookies like GA for WC cart to work.

Best regards,
Günter

• This reply was modified 4 years, 11 months ago by Günter.

Hi,

@Blatze

Please check https://kriesi.at/documentation/enfold/privacy-cookies/#default-cookie-and-services-option-settings for a closer description to “Default Cookie Behaviour”.

As it says: User must opt in for Cookies to work.

There are browser and js security restrictions to access and remove cookies – you only get info about the cookie name, but not the path. Enfold tries to remove cookies only in path “/” by default. As my dev surrunding is on a localhost the site is called with localhost/xxxx – and WC adds their cookies to path xxx. Therefore the cart worked for me, on your site WC uses path “/” and therefore cart cookies are removed – as expected until accepted.

As long as user does not explicitly accept cookies – or if user disallows cookies later – Enfold removes them if possible. We decided to use this strict implementation to be on the safe side for all users.

What you are talking about would be an option: Accept essential cookies on pageload, user must opt in for other cookies.

I will add this feature request to our repo and will check with Kriesi for an oncoming release.

Best regards,
Günter

Hi!

@Guenni007

Thanks for reporting this.

Translations are normaly provided by users – but I updated the de_DE file.
And I added the CSS for the iframe.

Will be in next update 4.7.1.1 – should be rekeased today afternoon,

@Studio-ADE

This is a mistake in the translation file (all 3 options are translated to same string – so they overwrite each other and only “Elements” is remaining.
I fixed it in the fr_FR fie.

Will be in next update 4.7.1.1 – should be rekeased today afternoon,

Best regards,
Günter

Hey Barnez1,

Thanks for using Enfold and for reporting this.

The plugin seems to call the WP filter widget_text with too few parameters. I added default values to our parameter list – this should fix the problem.

Will be part of the next update.

Meanwhile 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_1/function-set-avia-frontend.php

Best regards,
Günter

Hi,

I’ve been in backend – deactivated all plugins – and also switched to 2020 standard WP theme. The problem consists also for 2020 and no plugins active. – so nothing Enfold specific.

You need to rerun SSL-Migration.

I will ask the team if they have any idea – maybe you can check with your hoster if he knows something.

Best regards,
Günter

Hi,

It works with all settings Enfold offers.

Can you please provide us the user id so we can check from our server?

We do not have an problems with our test is’s we have. So it is hard to locate and fix the problem.

As far as I know Instagram has limitations for access. It could be that if you are using a shared hoster this IP address could be blocked because of too much traffic.

Best regards,
Günter

Hi,

I tried to reproduce the problem on my dev server – not able. It works fine for me also when refusing cookies.

I see js errors from a button plugin.

Also I see, that paypal is adding and deleting cookies.

Try to disable all plugins except Enfold and WooCommerce – clear server and browser cache and check. Then enable one plugin after the other and check.

And also have the developer console open and check for js errors.

Best regards,
Günter

Hi,

Please provide wp admin login credentials in private content so we can check your backend. We need to disable all plugins temporarily.

Best regards,
Günter

Hi,

Can you try to use something like:

$cookie_contents = 'This is my cookie contents for all sites.';

If this does not work, can you give us wp admin backend access so we can check and try to modify the code. We might need to add some debugging output.

Best regards,
Günter

Hi,

@achhee

Auf welcher Seite tritt das Problem auf?

Am besten versucht Du einmal eine neue leere Seite anzulegen und fügst dann ein Element nach dem anderen dazu. Kann sein, dass es irgend ein Problem mit special characters in optionen ist oder unclosed HTML tags.

Best regards,
Günter