MokoConsulting/MokoSuiteRealty
1
0
Fork 0
generated from MokoConsulting/Template-Joomla
Code Issues 11 Pull Requests Releases 1 Wiki Activity

feat: Google Maps integration — property map embeds, Street View, geocoding #11

New Issue
Open
opened 2026-06-23 14:11:47 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-23 14:11:47 +00:00
Owner
Copy Link
Copy Source

Summary

Add Google Maps integration for property display, address validation, and neighborhood context.

Requirements

  • Property map embed — interactive map on listing detail page showing property location
  • Street View — embedded Street View on listing page (uses existing lat/lng)
  • Geocoding — auto-geocode address on listing save (populate latitude/longitude)
  • Neighborhood amenities — nearby places (schools, grocery, transit) via Places API
  • Map on search results — map view alongside list view in property search

Technical Notes

  • PropertySearchHelper already stores lat/lng on listings — geocoding fills these on save
  • Maps JavaScript API + Street View + Places API
  • API key in plugin config (google_maps_api_key field)
  • Leaflet.js fallback for sites without Google Maps API key (OpenStreetMap tiles)
## Summary Add Google Maps integration for property display, address validation, and neighborhood context. ## Requirements - **Property map embed** — interactive map on listing detail page showing property location - **Street View** — embedded Street View on listing page (uses existing lat/lng) - **Geocoding** — auto-geocode address on listing save (populate latitude/longitude) - **Neighborhood amenities** — nearby places (schools, grocery, transit) via Places API - **Map on search results** — map view alongside list view in property search ## Technical Notes - PropertySearchHelper already stores lat/lng on listings — geocoding fills these on save - Maps JavaScript API + Street View + Places API - API key in plugin config (`google_maps_api_key` field) - Leaflet.js fallback for sites without Google Maps API key (OpenStreetMap tiles)
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteRealty#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?