Skip to content
MapSVG 9/Documentation

Troubleshooting

Start with the selected App, draft, device profile, and data binding. Many apparent display bugs are configuration or scope mismatches.

Choose Arrow, not Hand, below the preview. Then check Region → Settings → Disable all regions, matching Data rules’ Disable boxes, and exception interaction settings. An excluded SVG node is not a region even if it remains visible in the drawing.

Check that the Object appears in the Page’s Query result, that the Query returns Location, that its coordinates are valid and within the view, and that its marker image is accessible. A Region record does not produce a Location marker.

Confirm both use the same Page binding. Check the Query’s filters, projection, sorting, and page size. A hidden pagination control does not remove a page-size limit.

Autosave updates the draft. Publish releases its configuration. Confirm the shortcode’s App ID and any pinned version parameter, then check frontend caching. Record/Query changes are shared independently of App Publish.

Reload after checking your WordPress login session. A “Cookie check failed” response concerns WordPress REST authentication, not a tracking-cookie requirement. If it persists, inspect nonce/session requests and the browser console.

Do not clear site storage while it may contain your only unsynchronized draft. Read Offline editing first.

Check the specific console error, API key restrictions, enabled services, and geographic calibration. An SVG-only map does not need Google. An ordinary calibrated SVG and a downloaded Google screenshot template have different creation requirements.

Start its template with {{title}}, check Region versus Object context, and verify the required fields are returned by the selected Query. Test Popover before investigating the currently limited Details action.

Include the MapSVG/base-module versions, WordPress version, browser, selected component and action, exact error, and steps from opening the App. Include a small screenshot of the affected panel and whether the problem also happens on the frontend. Do not send private keys, support tokens, or unsanitized customer data.