Justin (a11n)

Hi @brunopenner,

Thanks for reporting! We will investigate and release a fix today if necessary.

For context, do you know if you upgraded from the immediately previous version? Or directly from an earlier version (I see 3.1.11 in the error)?

Cheers,

Justin

Hi @sirrahikkala, just circling back to thank you for surfacing this issue. As mentioned in the associated GitHub issue, there was some newer content that just hadn’t been tagged correctly to appear in the Coupons knowledge base section. The issue has been resolved and any locally cached content should have expired by now, allowing the new content to be displayed. But please don’t hesitate to reply or create new topic if you continue to see old content!

Cheers!

Hi, thanks for reaching out with your questions.

Do you use custom themes to build your checkouts, or third-party gateway checkouts? In WooCommerce 8.7 the hook used to add the order attribution data to the checkout page was changed to woocommerce_checkout_after_customer_details, and it’s possible that some customizations never invoke the hook when generating the checkout page.

Cheers,
Justin

Hello Rune,

Thanks for taking the time to reach out. Can you confirm you’re referring to WooCommerce 8.7? Does the attribution information appear correctly in the metabox on the Order Edit page, or is it missing there as well?

Do you have a cookie/GDPR consent manager installed on your sites? Are you using a custom theme/page builder? To continue troubleshooting, could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.

You can also confirm that order attribution is capturing source information correctly by checking the values in the sbjs_* cookies created by WooCommerce.

Cheers,
Justin

Hi @garvilo, thanks for posting the follow-up, excellent work conflict testing ?? I hope you’re able to resolve the issue quickly. Have a nice weekend!

Hi @garvilo, sorry to hear that you’re unable to use the new Order Attribution feature. Let’s see if we can figure out the problem.

They would see notice of error in making an order when clicking the ‘Order’ button at checkout

Can you confirm that the order is correctly being stored, but the customer isn’t being redirected to the confirmation page? Can you clarify what error message is displayed?

It looks like you’re using Elementor and Checkout Field Editor, have you made many customizations to the checkout form?

Cheers

Hi @snuffybg,

Thanks for your question. At the moment there is no way to specify a set of allowable utm_source values. The utm_source parameter is fairly standard for attribution tracking, and in this feature only uses thevalue when an order is placed.

If a filter for allowable utm_source values (or a default value) is something you think would be useful, please consider adding it to the WooCommerce feature requests board: https://woo.com/feature-requests/woocommerce/

Cheers!

Hi @paccio94, thanks for reaching out. I understand you’re having trouble with the Order Attribution feature. I took a look at your page and this is what I noticed:

• The visit source is being captured correctly on arrival.
• When the customer goes to the checkout, the source information is added to the checkout form as additional fields. The additional fields on your checkout appear to be commented out in the HTML: https://d.pr/i/YhIfl7

If these fields are being displayed within HTML comments (as indicated by <!-- ), then the order attribution data cannot be inserted and stored when the order is processed.

Can you check your checkout page’s composition or any custom changes you made to your theme to see why this section of the checkout form is commented out / disabled?

Happy to continue troubleshooting if you need any more guidance!

Cheers

• This reply was modified 1 year, 1 month ago by Justin (a11n). Reason: Better wording

Hi @ryanbester77,

This is likely due to adding an excluded tag to a product that is currently synced to the facebook catalog.

Can you try changing the “Facebook sync” field to “Do not sync”?
https://d.pr/i/CrHAQ8

Let us know if you’re still unable to update the product.

Hi @infobeckon,

We have found that one of the latest releases has introduced a bug in the disconnect procedure. The fixed plugin will be released today, but in the meantime, if you can’t wait, there are two things that you can do to perform disconnection:

1. Downgrade the plugin to version 2.6.30 which you can download from here:https://downloads.www.ads-software.com/plugin/facebook-for-woocommerce.2.6.30.zip
The connection and disconnection is not affected in this version.

2. If you have access to the WP CLI you can use the following command on your server to reset internal connection values. This should allow you to reconnect:

wp eval-file - <<STDIN
<?php
\$o = facebook_for_woocommerce()->get_connection_handler();
\$ro = new ReflectionObject( \$o );
\$rm = \$ro->getMethod( 'disconnect' );
\$rm->setAccessible( true );
\$rm->invoke( \$o );
STDIN

Let us know how that goes!

Hi again @neilgee,

Thanks again for you report. Version 3.0.4 of the plugin has been released today and should resolve your issue. Please give it a try and let us know (one way or the other).

Regards,
Justin

Hi @neilgee,

We’re sorry to hear about your problem with the plugin. Please allow us little time to go through the issue and get back to you as soon as possible.

In the meantime it would be great if you could share your current System Status Report. You can get it by navigating to the WooCommerce / Status section of your site. Once there, click on the Get system report button and then copy it by clicking on the Copy for support button. Then paste it here in a comment.

Thanks,
Justin

Hi @atomicrange1,

We’re sorry to hear about the issues you’re having with Google Listings & Ads! Here are a few things we recommend trying:

> 2021-06-25T00:26:36+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 1310720 bytes) in /var/www/wp-includes/cron.php on line 1144

This is a memory limit error – it looks like your host/site has a 128MB limit. We recommend a minimum of 256MB, and more if possible. The product synchronization process is fairly resource-intensive and raising that limit should resolve your errors.

If you’re not able to increase the memory available, you can try reducing the batch size (number of products synchronized at a time) by adding this filter:
add_filter( 'woocommerce_gla_batched_job_size', function( $size, $name ) { return 20; }, 10, 2 );

Cheers
Justin

Hi @konjx,

We’re happy to hear that you were able to get Merchant Center connected and running! But less pleased about the problems with the Ads account ??

{"statusCode":400,"error":"Bad Request","message":"Unable to create link for the customer account"}
This error makes us think that there may be some permissions issues with the Ads account – does the connected Google account have full access to the Ads account? If not, you’ll need to grant full permission before connecting. Otherwise, you might try creating a new Ads account using through the Google Listings & Ads extension.

Is there a way to reset the settings, try deactivating and deleting the plugin, then reinstalling it, yet the error is still there.

It looks like your Google account may have become disconnected. We’re working on a fix for situations like this, but for know your best option would be to follow the instructions in this comment: https://github.com/woocommerce/google-listings-and-ads/issues/486#issuecomment-861451332. That should reset your Merchant Center connection and allow you to go through the onboarding again.

Please let us know if your problems persists!

Cheers
Justin

Hi @electronee

Thanks for writing and sorry to hear about the problems when submitting your products to Google Merchant Center.

This issue when uploading products with descriptions that contain shortcodes was previously reported by another user, and the good news is that a fix will be included in the coming v1.1 release, as early as the end of this week.

Please update when the version becomes available, and let us know if you still encounter the issue.