negapo

Have also found this meta keys that i dont know if they were inserted by your plug-in:

fb_image
fb_product_description
fb_product_group_id
fb_product_image
fb_product_item_id
fb_product_price
fb_visibility

Hi @amandasjackson

I cant understand why are you selecting a random variation image for the main product image on variable products, this is nonsense. How can we set the main product image on facebook as the main product image on Woo and let the variations have their own image. This is how Woo is set up:

Variable Product: Has a main image called “product image” that is the image that appears on the “catalog”
– Variation 1 – Has its own image
– Variation 2 – Has its own image
– Variation 3 – Has its own image

I know there is an option to set up the variation image as the main product image but that’s not what a lot a people are complaining, they want the main product image on a variable product to be …. the main product image on Woo.

Image this, you have a necklace that comes in three colors, so you create a variable product on Woo with three variations: Yellow, Black and White. Then you take a picture of the three necklaces together that you set up as the product image, and then you take another three pics, one of the black, one of the white and one of the yellow and you set up each one of them to the corresponding variation.

Then the facebook plug-in syncs the product and you get your main product image as the yellow one. But why? why isnt the main product image used, the one that has the three options on the same pic?

Please help us out. Thanks

I’m also experiencing this memory leak, we have a VPS with plenty of CPU and RAM and the plug-in is retrying a failed schedule action to sync every 3 minutes and fails while exhausting the RAM.
In our case it seams a conflict with SiteGround optimizer plug-in (SG Optimizer), more precisely with Memcache. I saw the github issue but im not sure if its the same thing. I havent tried the workaround with the json file, i just disabled sync for now.

Thanks Sunday,

I do understand the upside of using unique names for the same images but in my case the downside of having plus 20 requests for images would be worse with the amount of traffic we get. But i will set up the images on the all variations even when they are the same as the main product images.
Regards

Our Stripe gateway also stopped working on 5.7.9

Its a menu in your Cloudflare account (if you have one). But if your site is running fine now you dont need to take that extra step.

Hi @hbk747
Sure, no problem
1. Log-In to cloudflare.com and chose the desired Domain (probably you just have one like me)
2. On the top menu bar chose “Workers”
3. There should be a table with the columns “Route and “Worker” where the route shows something like “https://www.YourDomain.com/*”
4. Click on “edit” on the right side
5. A pop up should appear, on the option “Worker” select “none”, then click save.

Thats it, hope it helps.

@shaileshwar Great, just one thing you should do now, go to your cloudflare account – chose your domain besthomeequip.com, then click on the “Workers” menu, there should be a route for “besthomeequip.com/*”, click on edit, “Worker – None”, click on save.

I didnt had the page cached, it was the first time i visited the page. Tried with pagespeed, it also renders the page fine. Did you enabled the recent “cloudflare” option on SG Optimizer?

Hi @shaileshwar , the site seems ok to me, did you disable SG Optimizer?

@giac You can choose the way CloudFlare handles when you have reached the limit, the default option is to “fail”, but there is an option to disable the worker when the limit is reached so you can have the benefit of the worker and then when the limit is reached it will revert. You can check that option on the CloudFlare account.

Hi @hbk747
Dont know how things are currently but on the first version of the SG Optimizer when “Cloudflare Full Page Caching” as introduced even if you disabled the feature after it was once activated the Worker that the plug-in creates on your CloudFlare account was still there active. Yuo have to go on to your Cloudflare page and manually disable (or delete) the worker.

We are also running on this issue, costumers can buy out of stock variations and some in stock variations cannot be added to the cart. We tried to debug conflicts between plug-ins with no luck. We have disabled SG Optimizer, but we tracked the issue to be with the “Remove Query Strings From Static Resources” option, when turned on it raises this issue. We had this option on for a long time with no problems.

Sure, email sent. Thanks

Just to add, this is the message:

Error 1101 Ray ID: 5ebd5067da595d3b ? 2020-11-02 10:53:50 UTC
Worker threw exception
What happened?
You’ve requested a page on a website (www.bean.pt) that is on the Cloudflare network. An unknown error occurred while rendering the page.

What can I do?
If you are the owner of this website:
you should login to Cloudflare and check the error logs for https://www.bean.pt.