8 docs tagged with "3.10.0"

Whether to render info-window content on demand (on marker click) instead of up front.

The number of markers above which info-window content is lazy-loaded on click.

Whether to render the visible directory entry list alongside the map. Map markers are built independently of this loop, so disabling it keeps every pin while dropping the per-entry HTML — a large payload and render-time saving on big, map-only layouts whose entry list is hidden anyway.

Whether to load map markers per viewport (on demand) instead of placing every entry up front.

Filters the bounding box used to frame a viewport map's initial (bare-URL) view. Return null to skip auto-framing so the map uses its configured center/zoom instead.

The visibility context that segments the dataset-bounds cache. Defaults to logged-in vs public; return a more specific token (e.g. a user ID or role hash) for Views whose visible entries vary per user via Advanced Filters or capabilities.

Maximum entries scanned when computing a viewport map's dataset bounds. Very large Views get approximate framing; raise this or supply bounds via the dataset-bounds filter for exactness.

How many entries a viewport Map View's initial page loads (markers load via REST). The entries themselves are not displayed, so a small number keeps the page fast. This caps the SQL row count only; page_size and the total count are unchanged.