jesperh95

Hi,

Yes, I updated the database right after updating the plugin – and I received a message that the database update was done before I checked the frontend homepage. When I then checked the frontend homepage I saw the error message. I refreshed the page, and it was gone again. Then I checked on another device (not logged in), and received the same error message. But I just received the error message once on each device. When refreshing the page, the error message was gone. When I check in incognito (no prior session), I do not receive the error message.

So to me it seems like this error message could maybe be shown once to all users of the site which have a session already before the update to 8.9.0. And I my case it did not seem like it was directly connected to the database update, since it was done before I checked the frontend homepage and received the error messages.

I also experience this issue after updating to Woocommerce version 8.9.0. I have experienced this error message on the frontend homepage multiple times on several devices, both logged-in and not logged in.

Hi Frank,

Thanks for the quick reply! ??

I tried your suggestion and can see it is a JS problem.

Is there a way to exclude 3rd party urls from being optimized, because from reading about similar issues with the minify JS option in WP rocket, I can see it could make sense to exclude the following:

consent.cookiebot.com
consentcdn.cookiebot.com

Best regards, Jesper

Hi John,

I am experiencing the same issue – did it help to re-install?

Best regards

Hi,

I see it happens (when orders are cancelled) no matter if it has a gift card or not. Besides this, the error log shows this critical error also happens every hour exactly.

I have WP/WC in latest version and also yith gift cards plugin in 2.11 version

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

Hi,

I experience the same issue after updating to the latest version of the plugin: “Uncaught Error: Call to undefined method YITH_WooCommerce_Gift_Cards::order_cancelled_action()”. It happens on line 537 in the file “/plugins/yith-woocommerce-gift-cards/includes/admin/class-yith-ywgc-backend.php”

I experience this fatal error both when I delete an order in the back-end, and also when customers themselves delete the order in the check-out process.

So this seems like a general issue with the plugin after laste update – I really hope you can help with this issue. Thanks ??

Best regards

Hi Kwesi,

Thank you for your reply.

I think there are issues in this, especially since in Woocommerce, you cannot set the same SKU (Stock Keeping Unit) for different products. But if you have a larger store, then for different brands the SKU could be the same in theory. In my store there are several of these examples. For instance 2 different brands could have the SKU “KIT012” for a product. This is also one reason why the SKU field makes sense to use as a warehouse place indicator instead, since products cannot be at exactly the same spot in the warehouse, so therefore this functionality (that the SKU has to be unique in Woocommerce) makes sense here.

In reality the SKU provided by the supplier does also change some times, and other times you will discover later that the first SKU you inserted is wrong or misspelled, or you forgot to insert a SKU when you first created the product etc. So just like changing the product name does not create a dublicate product, I do not think there is a reason for why changing the SKU should.

Besides this, the FB content_id should in the end just be a unique ID, so I do not see the reason why it is necessary for it to include the SKU anyway, as long as the post ID of the products can just be used (which it also is already when SKU is absent).

I agree that many probably use the SKU field as you say (which though could still give issues as explained above). And even if they use it as I do, many do not change the warehouse location frequently enough that it has any huge impact anyway, and if it has happened many are probably not aware. This is why I suggest that the Facebook for Woocommerce plugin just provides a bit of flexibility on this issue, since in the end it does not matter whether the SKU is in the content_id anyway. This could be solved by implementing the suggested filter. Then the user of the plugin can decide whether or not the SKU field should have any impact on the created content_id.

Please let me know whether I am missing anything in regards to why it should be important to include the SKU in the content_id, when it is not absent.

Hi Adam, thank you for this ?? Looking forward to hearing from you ??

Hi,

I am using the latest version 2.3.5, but this is not a new issue for me, it has been there for a long time now. It is only a problem if you ever change SKU’s, which in my case I do from time to time, as I use the SKU as the location in the warehouse, which can change.

Steps to reproduce:
– Change the SKU of the product in Woocommerce, update the product
– This creates a new product in the FB catalogue, the ”old product” is also still in the catalogue

So this is messing up the catalogue, since over time, if SKU’s are changed, dublicates are created. And I also guess this have an impact on advertising and retargeting, because people then will see old prices, outdated products, and products not in stock etc.

As I see it, it basically comes down to the function starting on line 92 in ”includes/fbutils.php”:

”public static function get_fb_retailer_id( $woo_product ) {
$woo_id = $woo_product->get_id();
// Call $woo_product->get_id() instead of ->id to account for Variable
// products, which have their own variant_ids.
return $woo_product->get_sku() ? $woo_product->get_sku() . ‘_’ .
$woo_id : self::FB_RETAILER_ID_PREFIX . $woo_id;
}”

This code includes the SKU in the content_id if a SKU exists, and only if there is no SKU, the content_id will be like ”wc_post_id_123” (123 is product id). I would prefer it to be like ”wc_post_id_123” all the time, so that it never changes, even if SKU is changed.
I would rather not edit directly in the plugin files, so a quick solution could be to include a filter in this function. Then the code could be modified through the filter if thats of interest, which it is in my case. People who never changes the SKU probably does not experience a problem.

So a solution could be to adjust the function to this:

”public static function get_fb_retailer_id( $woo_product ) {
$woo_id = $woo_product->get_id();
// Call $woo_product->get_id() instead of ->id to account for Variable
// products, which have their own variant_ids.
return apply_filters( ‘facebook_woocommerce_fb_retailer_id’, $woo_product->get_sku() ? $woo_product->get_sku() . ‘_’ . $woo_id : self::FB_RETAILER_ID_PREFIX . $woo_id, $woo_product);
}”

Please let me know whether it could possible to fix this issue ??

Hi,

I was about to compress all images on my woocommerce webshop through Bulk Optimization, when I ran into this thread – so now I have second thoughts about compressing the images if this can have a negative impact? It doesn’t seem ideal to have to add codes of line in functions.php for it to work?

Best,
Jesper

Hi,
I just downloaded the plugin again and now it works – thanks!

Sounds good! I just updated and it works ?? Thank you!

Hi Kevin,

I found version 4.3 in a backup I had – so I can’t even post a link, since it works fine again.

But an example of what was in one of the columns is:
<div style=”width: 100%; display: block; height: 220px; background-image: url(‘/photo.jpg’); background-position: right top; background-size: cover; background-repeat: no-repeat; padding: 25px 0 0 30px; margin-top: 10px;font-size: 28px; font-weight: 900; font-family: Montserrat; color: #ffffff; text-shadow: 0 0 5px #000000; cursor: hand;line-height: 28px;”>
Text here
</div>

Best Regards,
Jesper

Sorry, I meant version 4.3

Hi Hannah,

Unfortunately the page is in maintanance mode right now, but I have taken a screenshot: https://imgur.com/a/FIxvt

It probably happens because the product in column 3 in row 1 have a higher height that the other products, which somehow makes the products below not align.

I look forward to hearing from you! Thanks!

Best Regards,
Jesper