-
- AcyMailing
- Browser
- City
- Component Condition
- Continent Condition
- Convert Forms Conditions
- Cookie Condition
- Country Condition
- Date Condition
- Day of Week
- Device Condition
- Display Conditions
- E-Commerce Conditions (VirtueMart - HikaShop)
- EngageBox - Viewed Another Popup Condition
- Homepage
- IP Address Condition
- Joomla! Content Article Condition
- Joomla! Content Category Condition
- Joomla! Content Component View Condition
- K2 Category
- K2 Item
- K2 Page Type
- K2 Tag
- Language
- Menu Item
- Month
- New/Returning Visitor Condition
- Operating System
- Pageviews Condition
- PHP
- Referrer URL Condition
- Region
- Time on Site
- Time Range
- Trigger based on URL match
- URL Condition
- User Access Level Condition
- User Condition
- User Group
-
- Show a Floating Button After Popup is Closed
- Create Multilingual Popups
- Randomly Rotate Popups on a Page
- Αdd Sound Effects to Popup
- Make Accessible Popups
- Add Countdown Timer to Popup
- Limit impressions per unique visitor
- Test the responsiveness of your boxes for various devices and viewports
- Open a box by clicking on a menu item
- Trigger based on the minimum time visitor spent on the site
- Auto-Close Popup After a Specific Time
- Control Popup using HTML Attributes
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.
Recommended solutions
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:
- Forms: Convert Forms: Built and tested to work perfectly inside EngageBox popups.
- Galleries: Smile Pack Gallery Module: Fully compatible and optimized for popup use.
- Maps: Smile Pack Map Module: Works seamlessly within hidden containers like popups.
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.