"jQuery, or not jQuery, that is the question—
Whether 'tis nobler in the browser to suffer
The slings and arrows of Alpine directives
Or to take arms against a sea of selectors,
And by no framework end them."
— William Shakespeare.js
If Juicer Social is interfering with your website's functionality—broken navigation menus, misbehaving carousels, JavaScript errors—the cause is almost always a jQuery version conflict between your site and the Juicer embed. The fixes below are ordered from cleanest to most code-heavy.
⚠️ After making any of these changes, clear your browser cache (or test in an incognito window) before deciding whether the conflict is resolved.
Switch to a new feed design (recommended)
The cleanest fix is to switch to one of our newer feed designs. They're built to be lightweight and self-contained: they show your social posts on your page without loading jQuery — or any other heavy front-end framework — of their own. That means there's no version conflict with your site's scripts, the feed stays fast, and it won't interfere with how the rest of your site looks or behaves. For a full walkthrough, see Switching your feeds to the new Juicer design.
Open your feed's dashboard.
Click ⚡️ Switch to new feed in the top navigation.
Pick a template and customize the look and behavior of your feed.
When you're happy with the preview, click Apply new design.
✅ This is the recommended approach. No code changes, and you get access to our latest, most modern feed designs.
💡 For the technically curious: the new feed is server-rendered HTML enhanced with HTMX and a small amount of plain JavaScript — no third-party front-end framework, and no trouble with strict Content-Security-Policy setups.
Prefer to keep your current design?
Older feeds run on our legacy embed, which relies on jQuery — and that's where these conflicts come from. Rather than patching the legacy embed (something we're phasing out and no longer actively developing), the better long-term move is to switch to a new design, as described above — it sidesteps jQuery conflicts entirely and is where all our ongoing improvements land.
If you'd like to keep your current design — because of custom styling, a local implementation, or a specific look you've built around it — you can contact us and we'll help you migrate across without losing what matters to you.
Load a custom jQuery version
💡 This is a stopgap for the legacy embed, not a long-term fix. Since the legacy embed is being phased out, we'd still recommend migrating to a new design when you can — reach out and we'll help.
If your site doesn't have jQuery at all and you need the legacy embed working in the meantime, you can load a recent version before the Juicer embed:
<script src="https://code.jquery.com/jquery-3.7.1.min.js" integrity="sha256-/JqT3SQfawRcv/BIHPThkBvs0OEvtFFmqPF/lYI/Cxo=" crossorigin="anonymous"></script>
<script type="text/javascript" src="https://www.juicer.io/embed/YOUR-FEED-ID/embed-code.js?nojquery=true" async defer></script>
⚠️ Note: Replace YOUR-FEED-ID with your actual feed ID, visible in your Embed dialog.
Use the iframe embed
Open your feed's dashboard and click the Embed button in the top navigation. The iframe option is in that dialog; pasting its snippet into your site fully isolates Juicer from your site's JavaScript, so neither can interfere with the other.
⚠️ Feed embedded via iframe is not responsive by default and loses the post overlay feature. If you need responsive sizing, see Auto-resizing Juicer iframes to fit content.
WordPress users
If your site runs on WordPress, the cleanest path is the official Juicer WordPress plugin, which handles the embed for you and avoids most jQuery quirks. See Installing Juicer on a WordPress site for setup.
Drupal users
Drupal 10, 11 and 12 sites can use the official Juicer Social Feed module from drupal.org, which renders your feed as a configurable block with no code changes. See How to add Juicer to a Drupal site for setup.
Still seeing something break?
If you've tried the options above and the embed is still interfering with your site, the issue may be a CSS collision rather than a JavaScript conflict—a global style on your site bleeding into the Juicer widget, or vice versa. Send us a link to the affected page and we'll take a look; you can contact us from your dashboard or via the form on our website.