Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WPBakery Accordion Not Working: Causes and How to Fix It

WPBakery Accordion Not Working: Causes and How to Fix It

Short answer

A WPBakery accordion usually breaks because of a JavaScript error, an optimisation plugin delaying its scripts, duplicate section IDs, theme CSS, or wrong settings such as the active section. Check the browser console, exclude WPBakery scripts from delay, give each section a unique ID, and clear every cache.

Key takeaways

  • Check the browser console for JavaScript errors first.
  • Exclude WPBakery scripts from delay and combine options.
  • Give every accordion section a unique Section ID.
  • Review the active section and allow collapse all options.
  • Update the theme and bundled WPBakery together.
  • Test logged out after clearing every cache.

Why is the WPBakery accordion not working?

A WPBakery accordion usually stops working because of a JavaScript error, a script optimisation plugin delaying its files, duplicate section IDs, theme CSS conflicts, or wrong accordion settings.

The accordion needs JavaScript to open and close panels. When that script fails, panels either stay shut, all show open, or jump without animation.

Typical symptoms are titles that do nothing when clicked, every panel opening at once, the wrong panel opening, or the accordion working for logged-in users but not visitors.

Before you change anything, note exactly what happens and on which pages. That tells you whether the problem is site-wide or limited to one layout.

Is a JavaScript error stopping the accordion?

Check the browser console first, because any JavaScript error earlier on the page can stop WPBakery's accordion script from running at all.

Open the page, press F12, and switch to the Console tab. The Chrome DevTools console guide explains how to read the messages.

Red errors are what matter. Look at the file name in each error. If it points to another plugin, a theme script or a custom snippet, that is the likely cause even though the accordion is the part that looks broken.

Common sources are old jQuery code, a broken custom script in a header or footer plugin, and outdated add-ons for WPBakery.

Are optimisation plugins delaying WPBakery scripts?

Often they are: features that delay, defer or combine JavaScript can load the accordion script too late or in the wrong order.

Plugins such as WP Rocket, LiteSpeed Cache, Autoptimize and many others have options to delay JavaScript until a user interacts with the page. The accordion can then miss its first click, or never start.

Turn off delay, defer and combine options one at a time and test after each change. When the accordion starts working, you have found the setting.

You do not have to leave the feature off. Exclude WPBakery's JavaScript files and jQuery from that setting instead. Then clear the plugin's cache and test again.

Do duplicate section IDs break the accordion?

Yes; when you duplicate accordions or sections, they can end up with the same section ID, so clicking one title opens a panel in a different accordion.

Each accordion section has a Section ID field in its settings. It is used for the link between the title and the panel, and for anchor links.

HTML IDs must be unique on a page. The MDN reference for the id attribute explains why: the browser only finds the first element with a given ID.

Open each section's settings and give it a unique ID. This is the most common cause when the wrong panel opens or a second accordion copies the first one's behaviour.

Are the accordion's own settings set correctly?

Check the Active section and Allow collapse all options, because wrong values make the accordion look broken even when the script works.

Active section sets which panel opens on page load. If the number points to a section that does not exist, no panel opens. If you want everything closed at first, use a value that matches your theme's documented behaviour or leave it empty, depending on your WPBakery version.

Allow collapse all decides whether a visitor can close the open panel. When it is off, clicking the open title does nothing, which some people read as a fault.

Also check you are using the current Accordion element. Older sites may still use the deprecated legacy accordion, which some themes no longer support well.

Is your theme's CSS hiding or forcing panels open?

Theme or custom CSS can override WPBakery's panel styles, hiding content permanently or forcing every panel to stay visible.

Inspect a closed panel in your browser. If you see rules such as display: block or a fixed height from your theme stylesheet, they override the accordion's own state.

Switch to a default theme on a staging copy to confirm. If the accordion works there, the theme is the cause. Ask the theme developer, or remove the conflicting custom CSS.

Many commercial themes bundle WPBakery. Update the theme and the bundled plugin together, because an older theme can ship styles written for an older WPBakery version.

Is a plugin conflict or outdated version to blame?

Outdated WPBakery versions and conflicting plugins are common causes, so update first and then run a conflict test on staging.

Check the WPBakery version under Plugins. If it came bundled with a theme, you may need to update it through the theme's update process rather than your own licence.

Then, on a staging site, deactivate all plugins except WPBakery and test the accordion. Reactivate plugins one by one until it breaks again.

If WPBakery itself misbehaves beyond the accordion, our guide on WPBakery Page Builder not working covers wider checks.

If the editor is missing, see WPBakery backend editor not showing.

Could caching show an old broken version?

Yes; page caches and CDNs can keep serving old HTML or scripts after you fix the problem, so clear them before you test again.

Clear your caching plugin, any server cache from your host, and your CDN. Then test in a private window while logged out.

If the accordion only fails for visitors, caching or script optimisation is the likely cause, since many caching plugins skip logged-in users. Our guide on how to clear cache in WordPress lists each layer.

Does the accordion fail only on mobile?

When the accordion fails only on phones, look at responsive visibility settings, mobile-only caching and touch-specific script delays.

Some caching plugins keep a separate mobile cache. Clear it as well as the desktop cache.

Check whether the row or element is hidden on certain devices. Our guide on WPBakery responsive settings shows where those options live.

Also test with a real device rather than only the browser's mobile view. Touch events and mobile browsers sometimes behave differently.

Which fix matches your symptom?

Use this table to jump to the most likely fix based on what the accordion is doing.

SymptomLikely causeFirst fix
Titles do nothing when clickedJavaScript error or delayed scriptsCheck console, exclude WPBakery scripts from delay
Wrong panel opensDuplicate section IDsGive each section a unique ID
All panels open at onceTheme CSS or script not loadingInspect CSS and check console
No panel open on loadActive section settingSet a valid active section
Open panel will not closeAllow collapse all is offTurn the option on
Works logged in, fails for visitorsCache or optimisationClear caches and test logged out

When should you contact WPBakery or your theme developer?

Contact support when the accordion still fails on staging with only WPBakery active, or when the problem started right after a theme or plugin update.

WPBakery's knowledge base covers element settings and common issues. Licensed users can open a ticket through WPBakery's site.

If WPBakery came with your theme, the theme developer usually provides support for the bundled copy. Send them the page URL, console errors, and the versions of WordPress, WPBakery and the theme.

For background on building layouts with the plugin, see our guide on how to use WPBakery Page Builder.

Frequently asked questions

Why does my WPBakery accordion open the wrong section?

Duplicate section IDs are the usual cause. When you copy an accordion or section, the ID can be copied too. Give each section a unique ID in its settings, save the page, clear caches and test again.

How do I make all WPBakery accordion sections closed by default?

Turn on the option that allows all sections to collapse, then adjust the active section setting so no panel opens on load. How an empty value behaves can depend on your WPBakery version, so test the page after saving.

Can WP Rocket break the WPBakery accordion?

Yes, if JavaScript delay or combine options load WPBakery's scripts too late. Exclude WPBakery and jQuery files from those options, clear the cache, and test the accordion again while logged out.

Why does the accordion work in the editor but not on the live page?

The editor loads scripts differently and usually bypasses caching. On the live page, cached HTML, delayed scripts or a theme conflict can stop it. Clear caches, check the console, and test while logged out.

Is the old WPBakery accordion element still supported?

The legacy accordion element has been replaced by a newer accordion element. Old content may still work, but rebuilding it with the current element avoids styling and script problems in newer themes and plugin versions.

Sources

  1. WPBakery Knowledge Base WPBakery
  2. WPBakery Page Builder WPBakery
  3. Console overview Chrome for Developers
  4. id attribute MDN Web Docs
  5. Debugging in WordPress WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.