Third-Party Extensions Not Working Inside Popups

EngageBox allows you to display any Joomla Module, Shortcode, or Content Plugin inside a popup. This gives you the flexibility to load any widget, from forms and galleries to maps and custom scripts. However, while EngageBox provides the container and handles the popup’s display logic, it’s not responsible for how the embedded content will show or behave inside that container.

In most cases, if a widget works correctly when published directly in an article or module position but fails when placed in an EngageBox popup, the issue is related to how that third-party extension was built.

Why this happens

Popups work differently from regular page content: when the page first loads, EngageBox keeps the popup content hidden until a trigger (like on page load, on scroll, or on click) displays it. Some extensions are not designed with this behavior in mind. They expect their scripts to run immediately when the page loads and the element is visible. As a result, the widget may not initialize properly once it’s revealed later by the popup.

In short, the issue is not caused by EngageBox itself, but by how the embedded widget’s scripts are loaded within a hidden container.

For the best experience, we recommend using extensions designed with dynamic loading in mind and proven to work well inside EngageBox and popups in geneal:

Contact the developer of the affected widget

If you’re using another third-party extension and it doesn’t work properly inside a popup, reach out to its developer. Ask them whether their script supports being initialized in dynamically displayed (hidden → visible) containers.

Last updated on Oct 24th 2025 09:10