Controls, Layers, and Mobile Toolbar

These components provide navigation around the map. Select each under Map or in the Page tree as appropriate.

Controls

Controls settings include position and the enabled map buttons, such as Zoom, User location, Zoom reset, and Load previous map. A previous-map button needs navigation history; enabling it alone does not create a destination.

Test geographic zoom in Arrow mode. Canvas zoom below the preview scales the editor surface and is a different control.

Geolocation depends on browser permission and the site’s browser security context. Test the frontend behavior on the deployment environment.

Layers

Layers provides visitor-facing show/hide groups for SVG objects. Enable it, choose its position and initial expanded state, and add labeled items using the SVG-object selector.

A Layer item references SVG objects. It is not the same as a Layout container, a database filter, or a Page data binding. Hiding a layer changes visibility; it does not delete the underlying SVG nodes or database records.

Use clear labels such as “Service areas”. Test toggling the group off and on, and verify that its initial state matches your design after a reload.

Mobile Toolbar provides Map/List navigation on narrow layouts when the App uses a Directory. Its targets can be selected from the Page tree, or resolved automatically where supported.

New Apps place it in MobileFooter, hidden on Desktop/Tablet and visible on Mobile. Review this container’s responsive visibility when changing the default structure.

Select the intended Map and Directory targets for a more complex Page. The toolbar switches the visible content without needing a second independently configured App.

Test Map → List → Map after changing a filter or selecting a record. Visitors should be able to return without losing the relevant map context. Also check a mobile landscape viewport: its width may select the Tablet layout.

Publish component/configuration changes after testing all relevant layouts.