Complianz / Avada Bug report

If you look at the URL while in the live mode, what parameters do you see from Avada? For example, with Divi, we check if the url contains ?et_pb_preview=1

In that case, the cookie blocker is not activated, which is usually the cause of such conflicts, as often the inline javascript from these builders contain references to youtube etc.

If you can post the URL parameter here, we can add this in the plugin as well.

Hello,
thank you for your follow up.
the parameter is /?fb-edit=1
Best regards.

Hi @franck_b,

This parameter is already present in current versions of the plugin, so we’ll have to install the Avada theme on a test environment ourselves and take a look at what might cause this to occur.

Kind regards,
Jarno

Hi @franck_b,

We’re in contact with Avada, because we don’t know why our parameters would stop working. Could you try adding &cmplz_safe_mode=1 to the URL while in live mode and see if this works? This should do the same. Otherwise, try Safe Mode under settings. If both do not work, there’s another issue than our cookie blocker.

Hello,

In first thank you for your help.

i try &cmplz_safe_mode=1 but don’t work.

What i see is the windows from cookie consent who is open 2 times on page when i activate live edit. Content is not displayed, only header and footer. In consol i had this js error:

Uncaught SyntaxError: missing name after . operator mydomain.info:15703:67047
Uncaught ReferenceError: fusionAllElements is not defined
https://mydomain.info/wp-content/plugins/fusion-builder/front-end/fusion-frontend-combined.min.js?ver=3.9:1
https://mydomain.info/wp-content/plugins/fusion-builder/front-end/fusion-frontend-combined.min.js?ver=3.9:1
fusion-frontend-combined.min.js:1:783326
Uncaught SyntaxError: missing } after property list mydomain.info:17624:68321note: { opened at line 17624, column 68190mydomain.info:17624:68190
Uncaught ReferenceError: customizer is not defined
addToPanels https://mydomain.info/wp-content/themes/Avada/includes/avada-app/fusion-frontend-combined.min.js?ver=7.9:1
render https://mydomain.info/wp-content/themes/Avada/includes/avada-app/fusion-frontend-combined.min.js?ver=7.9:1
renderUI https://mydomain.info/wp-content/themes/Avada/includes/lib/inc/fusion-app/fusion-frontend-combined.min.js?ver=3.9:1
initialize https://mydomain.info/wp-content/themes/Avada/includes/lib/inc/fusion-app/fusion-frontend-combined.min.js?ver=3.9:1
Backbone 2
https://mydomain.info/wp-content/themes/Avada/includes/lib/inc/fusion-app/fusion-frontend-combined.min.js?ver=3.9:1
jQuery 13
fusion-frontend-combined.min.js:1:12023
Uncaught ReferenceError: fusionBuilderConfig is not defined
https://mydomain.info/wp-content/plugins/fusion-builder/front-end/fusion-frontend-combined.min.js?ver=3.9:1
jQuery 13
fusion-frontend-combined.min.js:1:251635
Uncaught SyntaxError: missing } after property list mydomain.info:965:100902note: { opened at line 965, column 100801doffice.info:965:100801
Uncaught SyntaxError: missing } after property list mydomain.info:2747:68321note: { opened at line 2747, column 68190doffice.info:2747:68190

screenshot with complianz in ?fb-edit=1&cmplz_safe_mode=1

https://tinyurl.com/2g9kvhn2

Hi @franck_b, It seems that something in the Avada builder has changed that removed our parameter. We have relayed the issue to Avada via GitHub. It would help if you could address the issue with Avada as well to get it solved. The complianz parameter stops the cookie blocker when using the Avada builder, so needs to be present.

We will share any updates in our communication with Avada here as well.

Kind regards, Leon

Hi!

Thanks for the amazing Plugin, first of all!

I am not sure from what you have written, if you were able to reproduce the error allready, so i am trying to describe a bit whats happening.

The Issue here is that they (Avada) are creating a hash in js which saves the content for the builder. All HTML is saved in Strings there so it needs to be escaped.

The Complianz Placeholder is not Escaped there (I guess because it got substituted after the processing by Avada), so it leads to an Js Error which stops the complete Builder to work.

The function is called initFusionAppInitialData();

Maybe it would be a way to detect if the overwitten part is escaped and if yes escape the Placeholder as well?

I am quite shure that could happen in other cases except for the Fusion Builder as well.

Regards Markus

Hi @markusand,

Thanks a bunch. We will have a look at this specific set-up.

regards Aert

I finally was able to reproduce the problem. It seems Avada has changed something, now they’re retrieving data with another parameter as well, ‘builder’ and builder_id, not just fb-edit. These page builders keep everybody busy ??

Because of this, the cookie blocker was loaded in the builder mode, which should not be the case.

The below should resolve the issue (added as mu-plugin), or you can try this branch:https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/avada-fix. Will get added to the plugin after it’s been tested and confirmed.

function rsp_my_add_new_avada($preview){
	if ( isset( $_GET['builder_id'] ) ) {
		return true;
	}
	return $preview;
}
add_filter( 'cmplz_is_preview', 'rsp_my_add_new_avada' );

Let me know if this resolves the issue!