-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update from 2.2.8 to 2.2.10 breaks site... #1182
Comments
The error on the page when it times out is:
|
Yes I agree. I haven't found any error messages yet but this update took down my site. Essentially the site worked fine until the customer attempted to add a product to the cart. At that point it would end up timing out. I had around 100 empty active carts and hundreds of 504 errors as the memory usage spiked. |
Further info, when adding an item to the cart..: – 2.2.8 works fine |
Hi @pixelmachine & @bossanova808 Could you try testing the latest commit for me in local development and let me know if this solves the issue. You can do this by updating your composer.json as follows:
It would be a big help, thanks! |
@nfourtythree tested, no errors for me – working as expected. |
Thanks for the quick response @pixelmachine really appreciate it. Will do some more testing and look to get a release out as soon as we can. |
Sorry for delay @nfourtythree, busy time of year.... can confirm it is also fixed for me with this change. I look forward to a release.....and I guess leave this open for others that may hit this, until you cut that release? |
Fixed in 2.2.11 - thanks! |
Description
If I update (via Composer Update) to 2.2.10 I immediately get time-out errors loading my site. Downgrading back to 2.2.8 fixes the issue.
Have you folks changed anything related to, or added more, logging? Any ideas where I should look?
In php_errors.log I find:
Feels like there might be some sort of infinite loop in serialising an object or something?
(I also updated Craft itself, but it's the Commerce update that seems to be the issue as it fixes itself if I revert just the Commerce updates)
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: