birdiedesign

Hi,

Thanks for replying. Fixed it by deleting WooCommerce Transients and clearing browser cache.

Best regards,
Michelle

Can somebody help?

Hi @xue28

Wow, great news. The problem is actually solved! Thanks a lot to all members of the support team for your help!

Best regards,
Michelle

Hi @beautyofcode

Thank you for your reply. I’ve tried your suggestion and unfortunately it doesn’t work. And yes, the issue persists when Elementor Pro is deactivated.

Kind regards,
Michelle

I still have this problem and still need help. I came across an error log in the server files and I see some error with WooCommerce. Not sure if it has anything to do with my problem. You can view them here: https://pastebin.com/cF1k7fP3.

Best regards,
Michelle

Hi @babylon1999

So I’ve heard back from my clients hosting and they are unable and probably unwilling to help. They claim it has nothing to do with their services and they can’t help us.

I’ve adjusted the wp-config file but of course this didn’t solve the problem. I have no idea how to solve this problem. Is there a possibility for you to check out the website on the backend if I can safely give you login details?

Best regards,
Michelle

Hi @babylon1999

Thanks for your reply. I appreciate your trying to help me!

I’ll contact my client and ask them to contact their hosting about the caching. They have managed hosting and I’ve wondered if that might have something to do with it.

There are quite a few error logs, but all are from before the problem started. Here they all are:

https://pastebin.com/5ki55zNL 15-04

https://pastebin.com/m42AQiCC 16-04

https://pastebin.com/p80gtVBz 17-04

https://pastebin.com/Z747NSxj 18-04

https://pastebin.com/6yzy784j 19-04

https://pastebin.com/8gzLnmrV 20-04

https://pastebin.com/zZwr3BCf 21-04

https://pastebin.com/Y8KJFsag 22-04

https://pastebin.com/Gc27wSTJ 23-04

https://pastebin.com/TWtEcV1g 24-04

https://pastebin.com/xuyzZzAj 25-04

https://pastebin.com/5u8FSfhV 26-04

https://pastebin.com/NFW8XX4M 27-04

https://pastebin.com/ss288KHD 28-04

https://pastebin.com/ScAfsxri 29-04

https://pastebin.com/U9HKN7Wi 30-04

https://pastebin.com/xgAwzS7M 01-05

https://pastebin.com/wagFXLwr 02-05

Most of them seem Astra and Elementor related. A few times the memory exhausted error, but I don’t think it’s related to this problem. My client has to pay extra for an increase in memory so I have to be sure that this will 100% fix it, before I suggest that.

Also I can’t figure out why the staging site does not have this problem and the live website does. Staging is a copy of the live site right? So how on earth is it possible that the staging site doesn’t have the problem, but the live website does?

Looking forward to hearing from you.

Best regards,
Michelle

My problem still isn’t solved so I still need help.

I’ve just noticed that when I go to Dashboard > Woocommerce the screen is blank. See screenshot: https://imgur.com/a/XKlzYcO

I’ve checked the javascript console again and now it does seem to give some errors. Here is the screenshot:

https://imgur.com/a/pO2zetz

No idea what it means, but does this have something to do with the problem?

Hi @fermarichal

Thanks for the reply!

I’m using Safari, but I’ve also tried to see if it would work in Chrome. Unfortunately I had the same results in Chrome.

I have tried to disable all plugins except WooCommerce before and have tried it now again, but the problem still persists. It’s not a plugin conflict or theme conflict as I have tested that by switching the astra theme for the default WordPress theme.

The steps:
1. I add a new product
2. I change from simple product to variable
3. I add attributes (I’ve tried both global attributes and creating a new attribute, both with same result). I’ve also noticed that the button to save the attributes is grey. It’s not looking clickable, but when I click on it it does save the attributes.
4. I try to add variations. Both buttons (generate variations and add manually) are not working.

I’ve also tried the above with an existing product and of course the problem also occurs.

I’ve also recorded my screen while doing the above. You can see that here: https://drive.google.com/file/d/127hXYtyZXjYm0L6htRlY2RxE_X8txTgq/view?usp=share_link

Like I mentioned before I’ve created a staging site and it’s so strange because then it does work and I can add variations. You would think this is an exact copy of the production site so how in the world is it possible that it is working on the staging site yet not at the production site?

Hope you can help me as this is driving me crazy.

• This reply was modified 1 year, 10 months ago by birdiedesign.
• This reply was modified 1 year, 10 months ago by birdiedesign. Reason: shared a wrong link

I have another update:

After downgrading the WooCommerce version to 7.6.1. I’ve updated WooCommerce again to the latest version. On the staging site variations work like they should after updating.

Here is the strange thing though. I’ve downgraded Woocommerce on my production website and as expected variations do work. Yet when I then update to the latest version (like I did on the staging site) the problem reoccurs and variations don’t work.

It’s clear something is going wrong when updating to the latest version, but the question is why does it work on the staging site and not the production site.

I’ve also used a staging site to downgrade to Woocommerce version 7.6.1. In this earlier version it is possible to add variations. So it must have something to do with the new update you would think.

Hi Jon,

Like @fallbrookian said it’s happening with new products, adding manually new attributes and existing products with existing attributes.

Best regards,
Michelle

Hi Jon,

Thanks for replying! I’ve checked the Javascript console and there aren’t any errors. It’s not the Variation Swatches plugin because the problem still persists when this plugin is switched off.

It’s so strange, because none of my other websites have this problem with pretty much the same setup in terms of plugins and theme. I have no idea what the problem is.

Best regards,
Michelle