the only thing i can think of, is the fact that somehow the site prevent the correct execution of event tracking only the basic of GA4

any suggestion?

Recently I noticed data not being accurate on my dashboard within Facebook.
My pixel shows active and I have confirmed activity within Extension.

The plugin is only showing up to View Content or Outbound cluck within the funnel.

It seems that when updates occur my plugin has issues. This happen quote often.

Has any one else experienced this? Also, would you think it’s best to hard-code instead of integrate with this plugin?

Hi this is for a client’s site so I’m not sure I want to share the domain here.

Basically, all the following events fire (using the Google Tag Manager preview panel):

begin_checkout
add_to_cart
set_checkout_options

.. I click on the order button which fires the process_checkout event and then loads the confirmation page:

https://mydomain/checkout/order-received/99188/?key=wc_order_8iEgyguAToICJ

The purchase event is just not there. The site is using the default order-received woocommerce template.

Any ideas?

Woocommerce 3.9.2
PixelYourSite Pro 7.3.10

Hope this will be fixed in the next update,
Thanks!

The only problem is that woocommerce isn’t firing the webhook to tell printify when a new order is made. Therefore, the orders aren’t automatically being fulfilled.

I reached out to Printify, and they responded with the following:
“Our Team Team got back to us.

They have checked your webhook resource and it appears that some sort of caching is occurring but it is not quite clear why that is happening. They assumed that cloudflare might be interfering in some way.

From the resource headers, they saw the following properties.

*X-XSS-Protection →*1; mode=block
*X-Cacheable →*YES:Forced

Nonetheless, it appeared that is not the issue from our side. It appeared that your order webhook does not trigger for some reason. If it were triggering in the first place, our logs would show if there were any other errors but nothing gets logged.

You will need to check from your side why this could be happening.”

I’m not experienced in websites or wordpress, so this is all a bit over my head. My husband is familiar, and I will pass any advice I get here onto him.

Any ideas on where I even start to fix this issue? To my knowledge, I’m not using cloudflare. What else can I check or do?

The only problem is that woocommerce isn’t firing the webhook to tell printify when a new order is made. Therefore, the orders aren’t automatically being fulfilled.

I reached out to Printify, and they responded with the following:
“Our Team Team got back to us.

They have checked your webhook resource and it appears that some sort of caching is occurring but it is not quite clear why that is happening. They assumed that cloudflare might be interfering in some way.

From the resource headers, they saw the following properties.

*X-XSS-Protection →*1; mode=block
*X-Cacheable →*YES:Forced

Nonetheless, it appeared that is not the issue from our side. It appeared that your order webhook does not trigger for some reason. If it were triggering in the first place, our logs would show if there were any other errors but nothing gets logged.

You will need to check from your side why this could be happening.”

I’m not experienced in websites or wordpress, so this is all a bit over my head. My husband is familiar, and I will pass any advice I get here onto him.

Any ideas on where I even start to fix this issue? To my knowledge, I’m not using cloudflare. What else can I check or do?

I built a plugin to handle custom post types. Within that plugin meta data should be modified if some requirements are met after modification of the post. When I hook to ‘save_post’ within the plugin it never gets fired, however if I simply move the add_action sentence to the child theme functions.php the hook is fired correctly.

Here is the code:

<?php
/*
Plugin Name: MDV CPT Plugin
Author: MDV
Version: 1.1
*/

defined( ‘ABSPATH’ ) or die( ‘This is a WordPress Plugin – No direct access permitted!’ );

add_action(‘save_post’, ‘validar_promocio_ini’,10,3);
add_action(‘edit_post’, ‘validar_promocio_ini’,10,3);

function validar_promocio_ini( $post_id , $post)
{

// Don’t run the echo if this is an auto save
if (defined(‘DOING_AUTOSAVE’) && DOING_AUTOSAVE )
return;

// If this is a revision, get real post ID
if ($parent_id = wp_is_post_revision( $post_id ) )
$post_id = $parent_id;

// Run only for events that go publish or future
$poststatus= get_post_status($post_id);
if ($poststatus !=’publish’ && $poststatus != ‘future’ )
return;

/* Based on some logic, update meta data */

return;
}

Could the problem depend on the load order of plugins vs functions.php?

Thanks

Zulok

Condition statement seems to work fine for (tested) home page, pages. But when I only want popup to work on a custom post type, it doesn’t seem to recognise the condition when I’m on the custom post type page.

I’ve tried “All Fantasy Packages” (fantasy package is the custom post type name), “Fantasy Packages: Selected” and “Fantasy Package: ID” – selecting any of these stops the overlay working ANYWHERE.

See below how I’ve registered my custom post type. I have another post type (Bespoke Fantasy Packages) and having the same issue. Thanks in advance for your help!

// let's create the function for the custom type
function fantasy_packages() {
	// creating (registering) the custom type
	register_post_type( 'fan_package', /* (https://codex.www.ads-software.com/Function_Reference/register_post_type) */
		// let's now add all the options for this post type
		array( 'labels' => array(
			'name' => __( 'Fantasy Packages', 'bonestheme' ), /* This is the Title of the Group */
			'singular_name' => __( 'Fantasy Package', 'bonestheme' ), /* This is the individual type */
			'all_items' => __( 'All Fantasy Packages', 'bonestheme' ), /* the all items menu item */
			'add_new' => __( 'Add New', 'bonestheme' ), /* The add new menu item */
			'add_new_item' => __( 'Add New Fantasy Package', 'bonestheme' ), /* Add New Display Title */
			'edit' => __( 'Edit', 'bonestheme' ), /* Edit Dialog */
			'edit_item' => __( 'Edit Fantasy Package', 'bonestheme' ), /* Edit Display Title */
			'new_item' => __( 'New Fantasy Package', 'bonestheme' ), /* New Display Title */
			'view_item' => __( 'View Fantasy Package', 'bonestheme' ), /* View Display Title */
			'search_items' => __( 'Search Fantasy Package', 'bonestheme' ), /* Search Custom Type Title */
			'not_found' =>  __( 'Nothing found in the Database.', 'bonestheme' ), /* This displays if there are no entries yet */
			'not_found_in_trash' => __( 'Nothing found in Trash', 'bonestheme' ), /* This displays if there is nothing in the trash */
			'parent_item_colon' => ''
			), /* end of arrays */
			'description' => __( 'Fantasy Packages', 'bonestheme' ), /* Custom Type Description */
			'public' => true,
			'publicly_queryable' => true,
			'exclude_from_search' => false,
			'show_ui' => true,
			'query_var' => true,
			'menu_position' => 8, /* this is what order you want it to appear in on the left hand side menu */
			'menu_icon' => get_stylesheet_directory_uri() . '/library/images/custom-post-icon.png', /* the icon for the custom post type menu */
			'rewrite'	=> array( 'slug' => 'fantasy-packages', 'with_front' => false ), /* you can specify its url slug */
			'has_archive' => 'custom_type', /* you can rename the slug here */
			'capability_type' => 'post',
			'hierarchical' => false,
			/* the next one is important, it tells what's enabled in the post editor */
			'supports' => array( 'title', 'editor', 'thumbnail', 'sticky')
		) /* end of options */
	); /* end of register post type */

https://www.ads-software.com/plugins/popup-maker/

add_action('save_post','save_post_test');
function save_post_test($post_id) {
	exit('saving');
}

It does fire when saving a post, but not pages/CPTs. Is there something I’ve missed in 4.0.1?

Edit: it gets weirder: i just edited wp-includes/post.php to exit() with output just before each (two) do_action('save_post'), but still nothing! how is that possible?? script does exit() when placed at beginning of wp_insert_post(), so I’m going to work my way down through the function and see where it returns.