Hi,

Enfold 4.6.2 is released – has the fix alredy in it – if you want to upgrade.

Best regards,
Günter

Hi,

Please update to 4.6.2 – just released.

There had been some fixes and backwards comp. issues since 4.6.1.

Best regards,
Günter

Hi,

@grafiko_at_62

Thanks for your feedback.

Enjoy the theme and have a nice day.

Feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

This problem is fixed in 4.6.2.

Please update, clear server cache and clear browser cache on mobile ( !!!! ).

Best regards,
Günter

Hi,

@Els

Welcome.

Seems to be a problem with Google and cookies on your browser. Next time try to use an incognito window for validating.

Enjoy the theme, have a nice day and feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

4.6.2 has been released – please try to update to this version.

Check your DSGVO/GDPR settings – they have been adopted to support “must opt in” and that user have to accept cookies (see theme option Default Cookie and Services Option Settings). Check our documentation.

When user has to accept cookies and services no cookies or services are allowed until he accepts cookies and services.

There are also new theme options for custom CSS, ID and heading styling: Theme Options -> Layout Builder -> Builder Options For Developers

There are 2 fixes for 4.6.2 that are not included in that version:

If you have problems with codeblock:

Replace enfold\config-templatebuilder\avia-shortcodes\codeblock.php with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_2/dev_fixes/codeblock.php

If with BlogPosts:

Reeplace enfold\config-templatebuilder\avia-shortcodes\blog\blog.php with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_2/dev_fixes/blog.php

Do not forget to keep a backup of the original file for a fallback – clear server and browser cache.
If you need assistance in updateing we need WP admin access and ftp access. Open a new thread and put it in private content.

Best regards,
Günter

Hi,

You’re welcome.

4.6.2 is released already.

Enjoy the theme, have a nice day and feel free to come back when you need further assistance.

Best regards,
Günter

Hey newki75,

Please refer to solution https://kriesi.at/support/topic/enfold-4-5-7-1-beta-2-form-missing-senders-email-address/#post-1136599.

Your from address is needed by some mail servers that block e-mails not having their address.

Normally the user email from the contact form is written in from, if you specify “Your from address” user email is written in reply-to.

ad 2) There is no mail data stored in a database – in this case user sent the contact form with an empty e-mail field.

Best regards,
Günter

Hi,

The line is commented (probably already in 4.6.2) and we will remove it in oncoming versions.

Best regards,
Günter

Hi,

Yes.

Missing sender e-mail has reason that form could be sent on mobile devices with empty email field. This is fixed in 4.6.2 (should be released soon).

Best regards,
Günter

Hi,

@middevon

Thanks for sharing this info.

Best regards,
Günter

Hi,

Thanks – this is caused because of missing cookies which are new since 4.6. You probably already accepted cookies in 4.5.7. This is a bug.

I added a fix for this in the next update.

A quick workaround would be to add a button with action “Do not accept and hide message bar” to the message bar, click this button, then open the modal window, check your settings and accept.

To fix it in core:

In file enfold\includes\helper-privacy.php around line 1366:

$cookie_contents = md5( $cookie_contents );

replace with:

$cookie_contents = md5( $cookie_contents ) . '||v1.0';

Around line 228:

			$option = $this->get_cookie_consent_message_bar_option();
			if( in_array( $option, array( 'message_bar', 'disabled' ) ) )
			{
				return;
			}

Below this insert:

			$cookie_accepted = isset( $_COOKIE['aviaCookieConsent'] );
			$cookie_allow_hide_bar = isset( $_COOKIE['aviaPrivacyRefuseCookiesHideBar'] );
			$cookie_essential_enabled = isset( $_COOKIE['aviaPrivacyEssentialCookiesEnabled'] );
			
			/**
			 * Check if we updated 
			 *		'||v1.0' from <= 4.5.7 to 4.6.2
			 */
			if( $cookie_accepted && ! ( $cookie_allow_hide_bar && $cookie_essential_enabled ) )
			{
				/**
				 * If user already accepted cookie we add our essential cookies so user can continue to use site without need to opt in for these explicit
				 */
				$cookie_accepted_value = $_COOKIE['aviaCookieConsent'];
				
				$sep = strrpos( $cookie_accepted_value, '||v' );
				
				if( false === $sep )
				{
					setcookie( 'aviaPrivacyRefuseCookiesHideBar', true, time() + YEAR_IN_SECONDS, '/' );
					setcookie( 'aviaPrivacyEssentialCookiesEnabled', true, time() + YEAR_IN_SECONDS, '/' );
				}
			}

I hope Kriesi will release 4.6.2 soon.

Do not forget to make a backup of the original file for a fallback, clear server and browser cache.

Best regards,
Günter

Hi,

@tigertoertchen

Thanks for the link.

I’m getting a Javascript error:

SyntaxError: unexpected token: identifier

Not sure, where this comes from as everything is minified.

We will release 4.6.2 very soon and a documentation for the updated DSGVO implementation 4.6.

As a first step please try to update to 4.6.1. (you can also try it with 4.6 – should work when you follow the following steps).

Uncheck “Modal Window with Privacy and Cookie Info” in theme options – this creates a CSS hidden content needed for the new DSGVO supporting must opt in. As you do not use a button to link to it it does disturb.

Then as a first step disable the minifying plugins and caching plugins, clear all server cache and check. You must accept cookies to hide the message bar.
Then step by step use caching and minifying.

Best regards,
Günter

Hi,

@Els

I logged into your site – and verification of reCaptcha worked. Just clicked the check button.

Also trying invalid keys returned correctly that they are invalid and I could revalidate with correct keys.

Best regards,
Günter

Hi,

@bonsaimedia

Strange.

I see you are using reCaptcha V3.

Can you try to deactivate it and check, if this solves the problem? As you are using enfold numeric captcha your form is protected.

Best regards,
Günter