Plugin conflicts

Progress Map Pro and standalone add-ons

Ultimate includes the core and all modules. Running old plugins at the same time causes class conflicts, double assets, and broken maps.

Do Don’t
Activate only Progress Map Ultimate Activate Ultimate + codespacing-progress-map
Enable modules under Ultimate Modules Keep standalone List & Filter / Draw / Nearby / etc. active
Follow Migration Upload old Pro ZIPs over Ultimate

If Ultimate shows a conflict notice, use Deactivate conflicting plugins immediately.

Caching & optimization plugins

Maps are sensitive to aggressive JavaScript optimization.

Try temporarily disabling:

  • Combine / minify / defer / delay of JS
  • “Remove unused CSS” that strips map styles
  • CDN options that rewrite or break query strings on map scripts
  • Rocket-like “Delay JavaScript execution” for Ultimate handles (cspm-*, terra-draw, Google Maps)

Exclude Ultimate and Google Maps scripts from optimization, then re-test.

Theme builders

  • Ensure the page actually processes shortcodes (Shortcode widget / module).
  • Avoid nesting maps inside elements that destroy/recreate DOM without re-init.
  • Test with a default theme (Twenty Twenty-*) to isolate theme CSS.

Multiple Google Maps loaders

Themes that load their own Maps API can clash. Prefer Ultimate’s loader — see Disable scripts & styles before turning Ultimate’s API off.

Checklist

  1. Only Ultimate active for Progress Map
  2. Optimizers excluded or disabled for a test
  3. Default theme test
  4. Debug modes if PHP/JS errors remain
Top