Customize appearance

Ultimate exposes branding controls so maps match your site without forking plugin CSS. Configure global colors in plugin settings and per-map options under Customize (and related style tabs).

Main colors

Set the primary colors used by map chrome: buttons, highlights, active states, and related UI accents.

Changes typically affect:

  • On-map tool buttons
  • Active filter / UI accents
  • Other elements wired to the plugin’s main color variables

After changing colors, purge CSS caches and hard-refresh the front end.

Slider & default marker / cluster colors

Fine-tune:

  • Slider controls used in search distance UIs
  • Default marker tint (when applicable to your marker mode)
  • Default cluster colors when using colored cluster styles

Custom uploaded marker/cluster images override flat color modes where images are in use.

Zoom control icons

Replace or restyle zoom in/out controls so they fit your design system.

Button order

Maps can show several tools (faceted search, radius search, countries, nearby POI, module tools, etc.).

  • Reorder top buttons
  • Reorder left buttons

Put the primary action first (for example Keyword Search or Faceted search on a directory home page).

Modal / pop-up behaviour

When Progressive Map opens content in a modal (single post in modal tutorials, nearby maps in modal, etc.):

  • Adjust modal size
  • Optionally force fullscreen modals

Test on mobile — fullscreen often works better for map-heavy dialogs.

Custom CSS

Use the plugin’s custom CSS field (when present) or your child theme for surgical overrides.

Good practices:

  • Prefix selectors with your map wrapper / page body class when possible
  • Avoid !important wars with minifiers
  • Don’t hide required accessibility controls
  • Document your overrides for future updates

Posts count

Optionally show how many posts/locations are currently available on the map — useful with filters so visitors see result counts.

Translation of UI strings

Core UI strings can be translated via:

  • Plugin settings translation fields (where available)
  • WPML
  • PoEdit / .po files

After plugin updates, re-merge translation files if required. Dedicated translation pages will live under Tutorials / module guides.

Checklist before going live

  1. Colors pass contrast checks on buttons and cluster text.
  2. Button order matches the story of the page.
  3. Custom CSS still applies after caching/minify.
  4. RTL sites: verify carousel mode and button layout.

Next steps

Top