Skip to main content

How a complete locator is composed

A published locator has one root Layout Design ID. The Layout does not contain hard-coded stores. It arranges widgets and stores references to other designs.

Layout (embedded on the page)
├── Search widget → Search form Design ID
├── Distance filter
├── Category filter → optional Category tile Design ID
├── Brand filter
├── Result count
├── Store List → Store Card Design ID
│ ├── optional selected-store detail → another Store Card ID
│ └── optional category drill-down → Category tile ID
└── Map
├── marker type: icon OR HTML card
├── HTML marker → Map marker Design ID or resolved assignment
└── marker popup → Map infobox Design ID

The Layout is what you embed

After saving a Layout, use its Copy shortcode action to copy:

[cliq_store_locator id="123"]

The same Layout can be selected in the Store Locator Gutenberg block, Elementor Store Locator widget, or WPBakery Store Locator element. Those embeds resolve the same Design ID; they do not create separate copies.

Widgets share one locator query

Search form fields, Distance filter, Category filter, Brand filter, and Store List controls update one query state. The Store List and Map consume the same results. Coordinates established by address search or visitor geolocation are used by radius filtering, distance sorting, cards, and map radius display.

This is why the controls must live inside the same Layout instance. Two separate embedded Layouts on one page have separate state.

Store Card and Store List are different things

The Store Card controls how one store looks. The Store List widget controls how many stores are requested and how those cards are arranged: list/grid, accordion, grouped accordion, or category drill-down; fixed scrolling; pagination; Load more; visible statuses; selected-store detail; filter drawer; and map-only toggle.

Marker and infobox are different things

The marker is what sits at the coordinate. An icon marker comes from the marker library. An HTML marker comes from a Map marker design. Selecting either marker opens a popup rendered from the Map infobox design selected in the Map widget or the default infobox.

Reference precedence

Widget selections are per-Layout. For example, the Store List's selected Store Card overrides the global Default store card for that locator. A Map-level forced marker overrides per-store, category, and global marker assignments for that Map widget only.

When moving a Layout between sites, export its referenced dependencies with it so imported Design IDs can be remapped.