Critical JS Error (slick.min.js) prevents Manual Ads from loading – Need urgent

display ads

Hi Support Team, Artem Temos

Please read this carefully. I am extremely frustrated as I have been trying to solve this ad rendering issue for over 2 months. I understand your standard protocol asks to “disable plugins,” but let me be very clear about the current situation so we don’t waste any more time:

1. Current Site State (Messy): My site currently has Google “Auto Ads” enabled ONLY to prove that my AdSense account is active and working. However, I DO NOT want to use Auto Ads. They are placing ads randomly, ruining my site’s layout and User Experience. It looks terrible.

2. Why I use “Ad Inserter”: I need the “Ad Inserter” plugin to place ads in specific, organized positions (Manual Placement). The problem is: When I try to use Ad Inserter for manual ads, they do not show up.

3. The Real Culprit (The Theme Bug): The issue is NOT the Ad Inserter plugin. The issue is the Uncaught TypeError: … slick.min.js error coming from the Woodmart theme on Single Post pages. This theme error breaks the JavaScript execution chain, causing 3rd-party scripts (like Ad Inserter) to fail.

4. What I have ALREADY done (So please don’t ask me to do it again):
– Updates: Woodmart Core and Theme are updated.
– Builder: I use Gutenberg (Native), NOT Elementor/WPBakery.
– Optimization: I do NOT use any heavy optimization/caching features that would alter script order.
– Testing: Even with clean settings, the slick.min.js error persists in the console.

My Request: I have already provided you with temporary admin access. PLEASE Log in now. DO NOT tell me to disable Ad Inserter, because that is the tool I need to use! Instead, please investigate why slick.min.js throws an error on Single Posts and fix it so that it stops blocking my Ad Inserter scripts.

I grant you full permission to disable/enable plugins for testing if needed, but the goal is to make Manual Ads via Ad Inserter work, not to remove them. Waiting for an urgent fix. !!! ? ? ? ? ?

Hello Artem, Thank you for your response. I am not a developer, so I tried to follow your advice to find the conflict. However, I discovered something very specific that proves the issue is within the theme itself.

To test this, I went to the Layout builder and simply added a standard “Woodmart Product Carousel” block (your native theme element) to the page. Here is the critical finding (please see the attached screenshot):

1. The Context: I want to emphasize that I am working within the standard Single Post Layout system provided by Woodmart. I have not modified any code or done anything custom. I am simply using the theme’s native builder features exactly as they are designed in your original templates.

2. The Trigger: As soon as I added your “Woodmart Product Carousel” to this standard layout, the Console immediately showed the red error: Uncaught TypeError: Cannot set properties of null (setting ‘textContent’).

The Impact: At the exact same moment this error appeared, my Manual AdSense unit (placed at the top) stopped displaying. My Question to you: Since I am strictly using your native element (Product Carousel) inside your native layout system, without any custom modifications, shouldn’t this work out-of-the-box?

If using your own standard elements in your own layout builder triggers a JS error that breaks the site, doesn’t this confirm the bug is in the theme’s code, not a plugin conflict?

I have provided the admin access in the private area previously. Could you please log in and verify this? I have left the Product Carousel on the page so you can see the error live. I have been struggling with this for 2 months. Please help me fix this theme bug. ! ? ! ! ! ! ? ? ? ? ? ?

Thank you for your response, but I must address your points precisely and firmly so we can solve this problem once and for all.

1. Regarding the Error Being “Completely Different”: The root cause that is breaking the site and killing the AdSense code is the Uncaught TypeError: Cannot set properties of null (setting ‘textContent’). This specific error has been persistent since I introduced the WoodMart Carousel element, and it remains the primary, fatal issue. It is the same core bug.

3. Regarding Disabling Plugins Again: I have already followed your instructions and performed the ultimate isolation test (despite the risk to my live site): I have deactivated all third-party plugins.

THE FINAL CONCLUSION IS UNMISTAKABLE (Proof by elimination): The Uncaught TypeError: Cannot set properties of null is STILL PRESENT in the Console when ONLY the WoodMart theme and your native Product Carousel element are active.

This proves with 100% certainty that the bug lies in the WoodMart theme’s core code when initializing the slider element, which then attempts to manipulate an element that doesn’t exist (null).

I have done everything you asked, and the evidence points directly to your theme. Please stop looking for external factors. I insist that you log in with the provided credentials and debug your theme code to fix this critical error immediately.