stevesand

Hi Meta.
We need a response regarding the above. As mentioned this is causing a significant waste of ad spend every time the plugin resyncs to the incorrect catalog. Kindly update us with a solution.

Another update after spending many hours investigating this issue.

The bug is worse than I first described. After checking all my sites, I found that the plugin randomly connects to the first pixel and catalog in the Meta account, ignoring the pixel selected during onboarding. It then sends tracking data and products to the wrong pixel and catalog for the wrong site.

Previously you could select a specific pixel and catalog during setup and this was working correctly. Something has changed, now you can only select the pixel but this selection is now ignored and replaced with the first pixel and its catalog in the account.

I checked my events in Facebook and realised that this issue has been ongoing for weeks, resulting in wrong tracking and ads showing incorrect products across sites. I have reinstalled the plugin many times now, cleared caches, and erased data, but the problem remains. The plugin will randomly chose the first pixel and catalog in the account.

The only current workaround is to manually replace the wrong pixel and catalog IDs in the database for each site.

Please fix this issue urgently as it is breaking tracking and has been wasting significant ad spend.

Thank you.

Hi, thank you for your quick reply and great plugin.

No, exclude rules have always used OR logic, include rules on the other hand used AND logic, called (include only). Maybe this is where the mix up stems from in the new update. The migration is converting the previous OR-logic to AND-logic for all exclude rules as if they used the same logic as the old include rules. You can confirm this by adding two different exclude rules and toggling between legacy and the new mode.

Thank you

• This reply was modified 8 months, 1 week ago by stevesand.

Hi again.

After spending some hours I found the bug in your update script.
You have a fantastic plugin, better than the competitors, but please please be more careful with your updates, this is the 4-5 time in the last 6 months that this plugin crashed from an update and my whole business goes down.

In your file:
Version_13_3_5_Update.php

This is only migrating the main site in a multisite setup, not taking other sites into account.
Your update function should look something like this:

public function run()
{
    // Check if we are in a multisite installation
    if (is_multisite()) {
        // Get all blogs/sites in the multisite
        $sites = get_sites();

        // Loop through each site
        foreach ($sites as $site) {
            // Switch to the subsite
            switch_to_blog($site->blog_id);

            // Perform the version check for each subsite
            if (
                (
                    version_compare(get_option(WOOCOMMERCESEA_OPTION_INSTALLED_VERSION), $this->version, '<=') ||
                    ! get_option(WOOCOMMERCESEA_OPTION_INSTALLED_VERSION)
                ) || $this->force_update
            ) {
                $this->update();
            }

            // Restore the current site after the update
            restore_current_blog();
        }
    } else {
        // Single-site update logic remains the same
        if (
            (
                version_compare(get_option(WOOCOMMERCESEA_OPTION_INSTALLED_VERSION), $this->version, '<=') ||
                ! get_option(WOOCOMMERCESEA_OPTION_INSTALLED_VERSION)
            ) || $this->force_update
        ) {
            $this->update();
        }
    }
}

Hi. We have rolled back and used 13.1.2 since this bug came in 13.1.13. Our wordpress was auto updated today and the bug was back again, dropping all our products from Merchant Center again. Is there a planned fix?

Hi, the bug is still present unfortunately.