psodfj

Hi @alexmigf
Thanks for the reply! I should’ve been clearer.
The checkbox and the VAT fields are custom fields added with a filter to woocommerce_checkout_fields here is how they look:

$fields['billing']['billing_to_company'] = array(
	'type'      => 'checkbox',
	'label'    => __( 'Do you want a company invoice?', 'woo-bg' ),
	'class'    => array(
	      'form-row-wide',
	),
	'id' => 'woo-billing-to-company',
	'priority' => 119,
);

$fields['billing']['billing_company_mol'] = array(
	'label'    => __( 'MOL', 'woo-bg' ),
	'required' => true,
	'class'    => array(
		'form-row-first',
		'woo-bg-company-info',
	),
	'id' => 'woo-bg-billing-company-mol',
	'priority' => 121,
);

I hope this answers your question.

PS. I think I figured it out. After taking a look at your classes/emails/class-woocommerce-catalog-enquiry-email.php it seems that the correct structure is:
child_theme/emails/woocommerce-catalog-enquiry-admin.php

It works now. Thanks

@wcmp Thanks for the reply!
Unfortunately, the template in my child theme is again not read. I have only changed “Product” to “Product Title” in the custom template to ensure it is correct but it is not being read and still the stock template is used. Permissions are standard 0644.

Here is the full path of the file:

public_html/wp-content/themes/generatepress_child/woocommerce-catalog-enquiry/emails/woocommerce-catalog-enquiry-admin.php

Thank you @aahulsebos and @paapst!
It’s staggering that most sites don’t abide to that.

Thanks Aert!
Ethically I agree, what’s optimal for business is another matter though ?? I would be very curious to hear what your lawyer will say. Can I subscribe somewhere so I don’t miss their response?

Thanks @aahulsebos!
Most sites I stumble upon show only an “Accept” button and “Settings” where tracking cookies are disabled by default. Then in Settings clicking “Save and accept” the user can accept only the functional.

Are you saying this behaviour is not GDPR compliant? Do you have a reference for the requirements for these elements on your website?

Many thanks!

Thanks @aahulsebos!

Thanks @aahulsebos, that’s indeed the tutorial I followed and linked to. So you can confirm that Google Analytics (anonymised) is GDPR compliant? Shouldn’t it be classified as “Statistics” or “Marketing” and hence be disable by default?

PS.
Also when implemented through Complianz the Google Tag Manager fails to verify ownership in the Google Search Console

PS. Or maybe integrate these events with Google Tag Manager?

Thanks for the reply!
Is there an easy way to integrate manually the enquire button or the “send” button with Google Analytics v4 which is based on events?

Thank you!

Hi @leonwimmenhoeve,
I found the script responsible for the cookies /wp-content/plugins/brizy/public/editor-build/165-wp/editor/js/preview.js but I can’t find Complianz’ “script center”. I read this article https://complianz.io/integrating-plugins/ but nothing like it exists in the Wizard under Integrations on our side.

How to block a specific script exactly?

Also, Complianz allows preference cookies as functional (I am referring to the pll_language cookie by Polylang). Cookiebot complains that they are accepted without consent and claims the site is not GDPR compliant. Whom should one trust? Does Complianz have a tool for checking GDPR compliance as a visitor like Cookiebot does?

Thanks!

• This reply was modified 4 years, 2 months ago by psodfj.

Thank you very much for your message there Leon!
Is there any way to force Complianz to block them for now? Perhaps they can be blocked by some php/js snippet?

It turned out I just had to pass proxy_set_header Accept-Encoding "gzip"; to the nginx reverse proxy.
All working now!

• This reply was modified 4 years, 11 months ago by psodfj.