Simon

Hi all!

Thanks for raising this issue, and thanks for the feedback so far. The option was created for the Google Product Category implementation, to allow specifying this for your synced products to help avoid errors in Commerce Manager and allow for better ad creation.

The list of categories itself is causing this to be a large option value as you’ve seen. We’ve raised this with our developers to see what improvements we can make to the implementation to avoid these types of issues going forwards, sorry once again for the problems this is causing!

While there isn’t a fix for this in the short term, it would be possible to revert back to plugin v2.0.5, before the categories were added, and remove the database option.

I’m sorry this isn’t the best news at this time! Is there anything else I can help out with?

Cheers,

Simon.

Hey @dekadinious,

Thanks so much for taking the time to leave a review, it’s much appreciated! The plugin is indeed linked to Facebook quite heavily for pixel tracking, and product syncing, so I can certainly see why this might have an effect on larger stores. Thanks so much for sharing this with me!

We’re always looking for ways we can improve upon the plugin, so I’ve made a note of this for our product team to consider in the future. For instance, one option might be to allow the turning off of pixel tracking for custom implementations such as you’ve mentioned, or perhaps allowing only certain events to be tracked instead to avoid those HTTP calls.

Again, thanks for passing this along, and thanks for giving the plugin a try!

Cheers,

Simon.

Hey @stapolin!

In the latest version, it is now possible to sync the same default variation selected in WooCommerce across to your catalog. This will happen automatically once you set the default variation in the WooCommerce edit screen: https://cloud.skyver.ge/mXu5d6LL

This should then show the correct variation price on the shop screen. If you’re having issues even after selecting the default variation, please do raise a new topic so we can have a look at your specific setup and what might be causing that!

Cheers,

Simon.

Many thanks @mrclayton!

Cheers,

Simon.

Hi @zahost,

Thanks for running those tests!

The console error is interesting as it suggests that WooCommerce hasn’t been able to load the scripts completely, which also suggests another conflict. The Internal Server Error should have produced some logging either with the WordPress debug logging, or within the PHP logs on your server too. If we could find out what that error is, that would definitely help us to track this down for you!

I can certainly appreciate it’s not always possible to fully conflict test on a live site. Would it be possible for us to get access to a staging site where we could look at this more closely?

Cheers!

Simon.

Hey @mgz069,

Great news! Thanks so much for confirming that for me. If you have any other questions, please don’t hesitate to reach out via these forums again, we’re happy to help!

Cheers,

Simon.

Hey @alohapirates,

Thanks so much for confirming that. A -1 error typically indicates an issue with how WordPress or WooCommerce has understood the URL request. We’ve seen a few issues recently where a merchant’s host settings were causing an error due to the long URL being used. It doesn’t look precisely the same as what you’re seeing here, though I wonder if it is related.

Do you, or your host, see any errors logged in the PHP logging or the fatal_error logs for WooCommerce after trying the connection?

Cheers!

Simon.

Hey @mgz069!

That’s right, though it would be great if you could test and let me know. In previous versions of the plugin we relied on the feed file to sync products, as we had no access to use the API. With v2.0.0, as we can now connect with Facebook’s latest API, we can now use their Batch Upload methods to sync your products.

This means that if you were to edit, create, or delete any products, it will trigger an API sync. You can also force a full refresh by syncing all products from the plugin settings screen.

Is there anything else I can help out with today?

Cheers!

Simon.

Hi @ezoodeen!

Thanks so much for passing over those screenshots. To confirm, none of the products within the Tudung Sarung category are syncing at the moment, is that right? Yet the other categories products are okay?

If so, that’s very strange, as it seems to suggest the connection to your catalog is okay if some products are being synced.

How many products do you see listed in your catalog when viewed through Commerce Manager? Would it be possible to send a screenshot of that too for me?

Cheers!

Simon.

Hey @jasonbnorth,

Thanks for writing in with your question!

We’re currently listening for two specific WooCommerce actions to track product ViewContent events. These are:

// ViewContent for individual products
add_action( 'woocommerce_after_single_product', [ $this, 'inject_view_content_event' ] );
add_action( 'woocommerce_after_single_product', [ $this, 'maybe_inject_search_event' ] );

Could you confirm for me that your theme is currently using these for the plugin to track correctly?

Cheers!

Simon.

Thanks for confirming @eisoku!

It would be great if you could raise your support question in the support forums so we could take a closer look! The WordPress guidelines ask that we don’t use review threads for support I’m afraid.

To follow on from Christine’s suggestion, it would also be great if you could run a quick conflict test before raising your support topic. It would be interesting to know if you see the same issue with only Facebook for WooCommerce and WooCommerce active, as it’s not something I’ve seen raised before.

Cheers!

Simon.

Hi @mgz069,

Thanks for confirming! As Jennifer mentioned, the new versions from 2.0.0 onward will use the API sync as the main method for syncing your products. You may not see this visible from the Catalog Manager though your products should still be synced.

Are you currently experiencing issues syncing your products after re-connecting with the latest plugin version?

Cheers!

Simon.

Hey @staceycampbell,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @sqdigital,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @anbroek99,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.