sanderrrrr

Hello,

thank you for the follow-up.
It seems strange that you are not familiar with GTM, since it is one of the core applications from Google. It is right up their with Google Analytics, and in many cases will work together with GA. I realize the inner workings and specific details might not be clear, but the integration of GA via GTM seems rather essential.

The issue is not about duplicate results, but about unnecessarily load times and code injection where that might not be necessary or relevant.

Anyway, my question is how your plugin works in coherency with GTM, but it seems that you simply do not offer a solution for that. In that case it might be better to switch from your plugin to a full GTM approach.

Thank you for your assistance so far.

Hello,

I assume many people would like to use both GTM and your plugin, and a recommendation how to optimize the both would be very helpful.

As you say you are not familiar with GTM, could you briefly elaborate how your code integration works and where you are injecting the GA code?

And for my other remark, please see the comment above from Shameem who shows to disable the Global Site Tag. However, in the newest version that has changed.

Apologies, I seem to have missed your earlier reply.

What I would like to do is use Google Tag Manager (due to a variety of reasons); and I am wondering about the compatibility with your plugin. Should I let GTM take care of the Google Analytics code, or should I let it run via the plugin.

I noticed the recent update also does not have the universal code checkbox anymore?

I put the link in my very first message: https://wpml.org/plugin/redirection/

In that sense it is WPML that claims your plugin is compatible with them. You are unaware of this?

—

And thank you for quick answer and the provided solution! On this link with the URL and Server I was able to solve it (Y)! https://redirection.me/support/matching-redirects/

WPML creates a virtual environment; meaning that visitors can visit de domain.bb but there is actually nothing hosted there. It is all hosted on domain.aa. So I can only edit/add/configure under domain.aa.

Your plugin states to be compatible with WPML, which is an odd thing if you have no knowledge of WPML?

I don’t think this is a solution to my question. My question is related to the use of WPML and Redirection plugin. As of now, they do NOT seem compatible as I cannot get this to work.

would you have a solution that actually fits my problem? Meaning a WPML site on multi-domain.

Yes, I am in: domain.aa/wp-admin/tools.php?page=redirection.php.

Then I click add new and want to add a new 301 redirection. I want to redirect a url on domain.bb (hosted via WPML) using this method. However, it does not seem to work. How can I create a redirection on domain.bb using your plugin and WPML?

How does it not work? I seem unable to provide the source URL as the domain name is different.

Hello,

thank you for the quick reply! That is great support. I am specifically talking about Google Tag Manager, not necessarily the integration of the analytics tag.

So if we want to use Googel Tag Manager, we would disable that box and integrate the code directly via Google Tag Manager? Or would this also disable other functionality of the plugin?

Any updates on this?
I see a related topic on Github:

https://github.com/woocommerce/woocommerce/issues/43829

Hello, do I understand correctly that this was a ‘mistake/bug’ and should be fixed in upcoming WordPress versions? Or why was this included in every page?

Also, if we remove the blocks-checkout.js from every page, it would still be removed from the checkout if we use the shortcode [woocommerce_checkout] if I am not mistaken, so I am not sure how this would resolve it?

Would a conditional dequeing not make more sense? For example as the code below (borrowed from google)

add_action( 'wp_enqueue_scripts', 'dequeue_blocks-checkout', 999 );
function dequeue_blocks-checkout() {
	if ( is_admin() || is_checkout() ) { 
		return ;
	}
	// Remove the scripts from the queue. 
	wp_dequeue_script( 'blocks-checkout' );

}

Thank you, appreciate the reply.
You don’t also happen to have used tables with the “ee_” structure?
For example _ee_product_feed or _ee_tiktok_catalog

Hello,

thank you for your follow-up. I indeed yesterday checked this image already. It DID exist, and I could not figure out what was wrong with it. However, I simply deleted it and I believe the error has been resolved.

Looking into another log file I noticed this was indeed related to thumbnail generation. I believe this image might have had a incorrect dimension or file size which may have causes this?

It seems for now the issue has been resolved.

Hello, that is understandable. The question is why there are still leftover entries in the first place, as we decided to uninstall and remove the plugin.

Would you be able to refer us to the the table_name or potential table_entries so we can search for them and clean?

Would you have any updates on this?
It still appears in the source code of the live environment:

<script type="rocketlazyloadscript">
window.wc_ga_pro = {};

window.wc_ga_pro.ajax_url = 'https://www.website.nl/wp-admin/admin-ajax.php';

window.wc_ga_pro.available_gateways = {"mollie_wc_gateway_ideal":"iDEAL","ppcp-gateway":"PayPal","mollie_wc_gateway_bancontact":"Bancontact","mollie_wc_gateway_banktransfer":"Bankoverdracht","mollie_wc_gateway_klarnapaylater":"Achteraf betalen (+\u20ac1)","mollie_wc_gateway_creditcard":"Creditcard (+\u20ac1)","mollie_wc_gateway_applepay":"Apple Pay","mollie_wc_gateway_belfius":"Belfius Direct Net","mollie_wc_gateway_sofort":"SOFORT Banking"};

// interpolate json by replacing placeholders with variables
window.wc_ga_pro.interpolate_json = function( object, variables ) {

	if ( ! variables ) {
		return object;
	}

	var j = JSON.stringify( object );

	for ( var k in variables ) {
		j = j.split( '{$' + k + '}' ).join( variables[ k ] );
	}

	return JSON.parse( j );
};

// return the title for a payment gateway
window.wc_ga_pro.get_payment_method_title = function( payment_method ) {
	return window.wc_ga_pro.available_gateways[ payment_method ] || payment_method;
};

// check if an email is valid
window.wc_ga_pro.is_valid_email = function( email ) {
  return /[^\s@]+@[^\s@]+\.[^\s@]+/.test( email );
};

</script>

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

Hello,

based on your recommendations i manually updated to version 2.0.0-test3.
How should I proceed?