Home / Forums / WoodMart support forum / Woodmart problems after update from version 8.2.7 to 8.3.0+
Home › Forums › WoodMart support forum › Woodmart problems after update from version 8.2.7 to 8.3.0+
Woodmart problems after update from version 8.2.7 to 8.3.0+
- This topic has 21 replies, 2 voices, and was last updated 1 hour, 25 minutes ago by
Artem Temos.
-
AuthorPosts
-
October 20, 2025 at 12:42 pm #691797
szymon-0481ParticipantHello,
After Woodmart theme update from 8.2.7 up – even to the current latest (8.3.3)
The homepage and single product page crash – like @ the screenshots.
Tried updating everything to the newest version – all plugins, woodmart core, patches.
Nothing helps.
Any ideas?
Urgent
Thank youAttachments:
You must be logged in to view attached files.October 20, 2025 at 12:50 pm #691805
szymon-0481Participantfurther imgs
Attachments:
You must be logged in to view attached files.October 20, 2025 at 1:03 pm #691811
Artem TemosKeymasterHello,
Could you please disable all plugins that are not related to our theme and provide us your admin access so we can check it?
Thank you in advance
October 20, 2025 at 2:02 pm #691822
szymon-0481ParticipantLogin details sent in private
This is dev site – please do what you need.
You’re allowed to disable plugins and do necessary tests.October 20, 2025 at 3:14 pm #691864
Artem TemosKeymasterPlease disable all plugins that are not related to our theme so we don’t break anything. Also, it seems to be affected by the custom CSS you added to Theme Settings. Please temporarily remove that CSS as well.
October 20, 2025 at 6:43 pm #691915
szymon-0481ParticipantDisabled all plugins except woodmart and elementor
Deleted all CSS
The problem still occurs.October 21, 2025 at 9:24 am #691951
Artem TemosKeymaster1. Go to Elementor -> Settings and enabled the
Optimized Markupoption https://monosnap.ai/file/TXQH1zOYex7qiJvV8wseYsABt8x43T2. As we can see, you still have some plugin that affects images and add some kind of lazy loading
October 21, 2025 at 12:05 pm #691997
szymon-0481ParticipantThat isn’t the issue.
The difference is, without these plugins, images are broken in the single product’s “related items” grid.
The page is broken nevertheless. (homepage and single product page)
That’s why I’ve activated these two back yesterday.
Now, they’re off – please have a look.
We’ve got woodmart core, elementor and woocommerce as the only active plugins.October 21, 2025 at 12:10 pm #692000
Artem TemosKeymasterNothing changed; we still see some optimizations applied to images on the product page. Here is a screenshot https://gyazo.com/b8a8fab0c8b03eeac24c73f15e0c3089
October 21, 2025 at 12:21 pm #692006
szymon-0481Participanthmm, honestly – no idea where it comes from…
Everything is switched off.
CSSes deleted
Code snippets (all custom code) off.October 21, 2025 at 12:41 pm #692012
Artem TemosKeymasterIt may be something related to the server optimization extensions. Consult with your server’s provider for help.
Kind Regards
October 21, 2025 at 12:44 pm #692013
szymon-0481ParticipantThe thing is, everything works normally if I rollback the theme to 8.2.7.
So why doesn’t it work with all the plugins, extensions, etc. with 8.3.0 and above?
I don’t think it’s something on our side, but rather something that was modified in the theme.October 21, 2025 at 12:49 pm #692016
Artem TemosKeymasterAnyway, this lazy loading affects the images and causes this issue. You need to disable it first and test how it works without it.
October 23, 2025 at 1:20 pm #692370
szymon-0481ParticipantDone some tests and the results are:
1. Images broken (stretched vertically) on the homepage and in single product layout are in fact broken by the current incompatibility with our server’s caching – I’ve tested the dev site on another server and it works good.
The question here is: What can we do about it? We still need the server caching as it has worked flawlessly until the 8.3.0+ update. We cannot get rid of it as our server is currently overwhelmed (in 1-2 weeks time we’re changing servers anyway, so we can wait with this issue until that time and see what happens after migrating to a new server)
2. The homepage’s section (only one, fortunately) is still broken – It has started behaving differently after the theme update. On the production site (woodmart v 8.2.7) it still works as normal, while on dev site (woodmart v 8.3.3) it’s broken – there’s nothing changed between them. I’ve reactivated all the plugins, CSS, code snippets, etc. and it stays like that all the time.
The only way to fix it is to change columns number in text editor from 2 to 1, but the previous design is the one we want to keep and there’s no way now to force the text editor to wrap the columns when there’s not enough inline space – and this is what happens – shown @ the screenshots – it just overflows, flooding the second container. What can we do about it?
Login details are still valid, so please feel free to login and have a look at it. (pages > home)
CheersAttachments:
You must be logged in to view attached files.October 23, 2025 at 1:22 pm #692373
szymon-0481ParticipantThis is what the columns should look like – a screenshot from a live site (woodmart v 8.2.7 ATM)
Attachments:
You must be logged in to view attached files.October 23, 2025 at 2:58 pm #692405
Artem TemosKeymasterHere is a custom CSS code to fix the thumbnails issue
.wd-gallery-thumb img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: auto 160px; object-fit: contain; }As for the home page, we see that you still use unoptimized markup. Please enable this option in Elementor settings https://monosnap.ai/file/sFepi4D9GBCkNHDeTaXvvRFJzR17Pq
October 23, 2025 at 4:39 pm #692431
szymon-0481ParticipantOk,
This CSS helped to fix the thumbnails. They’re square again (and they stay like that no matter how many times I refresh the page).
But, the problem comes up in many other places where imgs are present on the site – either product archive, related products in single product layout, etc.
Tried to improvise and modified the selector from:
“.wd-gallery-thumb img:is([sizes=”auto” i], [sizes^=”auto,” i])”
to:
“body img:is([sizes=”auto” i], [sizes^=”auto,” i])”
But it doesn’t behave super properly. It does feel like an “emergency medicine”, instead of proper tech collision fix. :/ When we fix it in one place, the problem shows up in a different one…
Do you have any idea what else can be the problem here? Why did it stop working suddenly after the update? If we could catch the core issue that causes it, it would be best to just eliminate the problem in the root.
Moreover, will this CSS rule work with old browsers? We’ve got a lot of customers using old PC’s, with old browsers installed.
Secondly, Homepage was also fixed by activating that function. Works alright.
Thank youAttachments:
You must be logged in to view attached files.October 24, 2025 at 9:26 am #692509
Artem TemosKeymasterHello,
In this case, we have to return to the lazy loading applied to all images on your website, as shown in the screenshot. Since our theme has its own optimized lazy loading, it doesn’t support any 3rd party lazy loading for images. You need to disable this option on your server; otherwise, you will have these problems with images everywhere

Kind Regards
October 24, 2025 at 12:15 pm #692554
szymon-0481ParticipantOk, understood.
Was this lazy loading of yours added in the 8.3.0 version? Because as I said – 8.2.7 works good on live sites.
We’ll wait until the migration and see what can be done with the server-side caching.
I won’t be updating the production until then.
I’ll keep you posted.
ThanksOctober 24, 2025 at 12:18 pm #692555
Artem TemosKeymasterNo, we had that function from the beginning. And we never declared support for third-party lazy loading. Actually, you don’t need to use them at all since our theme’s core lazy loading is the most optimized for performance.
October 24, 2025 at 12:58 pm #692564
szymon-0481ParticipantI’m just looking for a reason why it stopped working all of sudden after the update.
We’ve had it working for a year flawlessly on 10 shops simultaneously – on the same server, with same configuration.
Right now, if I rollback to 8.2.7, it works again.October 24, 2025 at 2:34 pm #692606
Artem TemosKeymasterCould you please send us a link to the page where you rolled back so we can check how it works?
-
AuthorPosts
- You must be logged in to create new topics. Login / Register