Joomla Map Extensions
Google Maps often reaches a Joomla page not as a raw iframe but through an extension — a page builder addon, an events component rendering a venue map, or a dedicated maps plugin. Smart Local Google Maps includes dedicated patterns for 13 of the most common of these so they are blocked without any extra configuration.
Built-in Extension Coverage
| Extension / source | Detected as |
|---|---|
| Joomla editor (TinyMCE / JCE) | Standard google.com/maps/embed iframe |
| Google Maps JavaScript API | maps.googleapis.com / maps.google.com/maps/api script tags |
| Widgetkit (YOOtheme) | Widgetkit map markup |
| YOOtheme Pro | uk-map elements |
| Gantry | Gantry map particles |
| SP Page Builder | sppb-addon-gmap addon markup |
| Advanced Page Builder | Map block markup |
| Phoca Maps | Phoca map markup |
| Mike Reumer Google Maps | Plugin map markup |
| BT Google Maps | Plugin map markup |
| MyMapList | Plugin map markup |
| DG Fotomap | Plugin map markup |
| JCal Pro | Event location maps |
| JEM (Event Manager) | Venue maps |
| Event Booking | Event location maps |
| Generic fallback | Any <div> with an id starting googlemap |
Because detection runs on the final rendered HTML, the plugin catches these regardless of which extension produced them — it matches the output, not the source extension. See Map Detection for the full pattern groups.
Adding Coverage for Other Extensions
If you use a map extension whose markup none of the built-in patterns match:
- Enable Debug Mode (Expert Mode tab), log in on the frontend as a Super User and load the page — confirm nothing matched
- View the page source and copy the HTML the extension outputs around the map
- Write a regex against it and paste it into the Custom Regex Pattern field
See Expert Mode for the full workflow and syntax rules.
A Note on JavaScript-Injected Maps
If an extension injects the map into the DOM client-side (via JavaScript after page load) rather than outputting it in the server HTML, the server-rendered markup may be clean while the browser still builds the map. In that case, target the initializing script or container with an Expert pattern — or replace the embed with a {smartmap} shortcode, which is consent-wrapped by construction and needs no detection. See Troubleshooting.