Archived topic
help needed! URGENT
7 replies · Started by johnaps on December 27, 2021
Hello!
in my product pages, when adding a product to cart, sometimes the layout gets broken!
if you make add to cart many times fast one after another in 5-12 tries you will definitely see the layout getting broken!
I have tried disabling all performance plugins and any plugins related to product pages (like comments plugin, yith plugins etc...), to no avail though. (Always clearing cache's with every change)
IMPORTANT: Its as if the custom layout i have made through code in my child functions.php isnt always being loaded, thus resulting in broken layout....
Any insight would be greatly appreciated!!
This is a video of the bug
https://drive.google.com/file/u/2/d/1B1yc2rBsl3zqeIDQur9HY4BUed0jhjmz/view
and in one of my tries i got this in my console
(index):196 Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, mailpoet-marketing-optin-block-editor-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
I furthermore have disabled mailpoet plugins based on the above console error, and i still have the problem...
While getting no errors on browser console...
Hi there,
i tested this on several browsers and not been able to replicate the issue - heres one of them:
Yes you may have found something...
I think the problem is only happening on chrome, now that mentioned it, (a quick test on mozilla didnt show up the problem...)
But i tried again on incognito chrome with no extensions... and the problem was there still
Hi there,
I've checked the site as well and I didn't encounter the issue mentioned.
I do notice how slow the assets load though. You may want to consider using an optimization plugin to improve this. :D
You checked with chrome??
The site is slow cause i have all optimization plugins disabled for testing xP, also it is a replica test site!
The video i shared above is the test i ran on the Chrome browser.
As a default we all test in Chrome, FF and Edge or Safari ( depending on our platform )
Neither Elvin or I could see the problem which points to a local issue.
