<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1876746335844462&amp;ev=PageView&amp;noscript=1">
Skip to content
  • There are no suggestions because the search field is empty.

Release Notes - 04/16/26

In CRM v1.1.1, CMS v1.3.2, and CMS v1.4.0, we closed 31 tickets focused on streamlining lead workflows and assignment, improving listing alerts and email visibility, enhancing website search and OmniSearch usability, boosting listing-details performance, and tightening navigation, URL handling, and location-boundary behavior across CRM and CMS.

In CRM v1.1.1, CMS v1.3.2, and CMS v1.4.0, we closed 31 tickets focused on streamlining CRM workflows and lead assignment, improving listing‑alert visibility and email filtering, and enhancing CMS search/OmniSearch UX, listing‑details performance, and navigation/URL reliability.

  • Total issues: 31

  • Bugs fixed: 18

  • Improvements / enhancements / new capabilities: 13

Release v1.1.1 – CRM Pipeline

This release improves CRM workflow consistency, listing‑alert presentation, and email visibility controls, while resolving several issues related to cloning behavior, ported‑number webhooks, and missing template merge fields.

Highlights

  • Removed the “Nurture” status from new lead‑source prefixed workflows to standardize workflow stages and simplify lead progression. (CRM-350)

  • Updated Listing Alerts card design for system use to improve readability and consistency for internal/system users. (CRM-340)

  • Implemented email filtering logic based on CRM contacts and agent access to reduce irrelevant or unauthorized email visibility. (CRM-227)

  • Fixed issues where cloned workflows defaulted lead assignment to the GGMS Demo Agency instead of the correct account owner, and restored Twilio webhook handling for ported numbers. (CRM-349, CRM-320)

Top issues and stability improvements

  • Removed the “Nurture” status from new lead‑source prefixed workflows to standardize workflow stages. (CRM-350)

  • Fixed cloned workflows defaulting lead assignment to the GGMS Demo Agency instead of the correct account owner. (CRM-349)

  • Updated Listing Alerts card design for system use to improve readability and consistency. (CRM-340)

  • Completed the number‑port request work to ensure proper setup and handling of the ported number. (CRM-325)

  • Fixed Twilio webhook handling for ported numbers to restore expected call and message processing. (CRM-320)

  • Restored missing template merge fields so CRM templates populate contact details correctly. (CRM-309)

  • Added missing CRM contact fields and expanded the audit to improve field consistency across accounts. (CRM-297)

  • Implemented backend support for email filtering based on CRM contacts and agent access to control which emails agents can see. (CRM-227)

Release v1.3.2 – Website (CMS)

This release improves OmniSearch clarity and the search‑widget experience, and resolves multiple UI/UX and performance issues across dashboards, maps, widgets, toasts, and editor mode.

Highlights

  • Updated OmniSearch suggestions so the user’s entered or matched search terms appear in bold for faster recognition. (GGMI-3586)

  • Enabled dynamic tags for Search Results Widget fields, including collection and geo‑coordinate fields, to support richer search configurations. (GGMI-3575)

  • Updated property‑type and standard‑status icons to better align with familiar real‑estate UX patterns (similar to Redfin/Zillow). (GGMI-3550)

  • Revamped the search‑widget design and fixed several UX issues affecting dashboards, map controls, and notifications. (GGMI-3515)

Top issues and stability improvements

  • Updated OmniSearch suggestions to bold the typed or matched text for better scanability. (GGMI-3586)

  • Fixed the “Any” filter option not being center‑aligned on mobile screens. (GGMI-3579)

  • Enabled dynamic tags for Search Results Widget fields, including collection and geo‑coordinates, to give sites more control over displayed metadata. (GGMI-3575)

  • Fixed a dashboard loading issue where a blank section appeared before skeleton loaders for Name and Created Date. (GGMI-3573)

  • Fixed an issue where signing out caused the page to reload twice. (GGMI-3572)

  • Ensured that when a user selects a recent search, the chosen value is correctly displayed in OmniSearch. (GGMI-3567)

  • Fixed a bug where a “saved search” confirmation toast appeared after a page refresh even when no changes were made. (GGMI-3566)

  • Corrected error toast icon sizing and alignment in OmniSearch when long input values are entered. (GGMI-3563)

  • Updated property‑type and standard‑status icons for a more familiar, industry‑standard look. (GGMI-3550)

  • Improved ListedBy widget performance so it loads more quickly on the page. (GGMI-3545)

  • Restored proper border styling for map zoom (+/−) controls. (GGMI-3523)

  • Revamped the search‑widget UI to enhance usability and visual consistency across devices. (GGMI-3515)

  • Fixed unexpected form re‑rendering during configuration in editor mode to reduce disruption while editing forms. (GGMI-3479)

Release v1.4.0 – Website (CMS)

This release improves global search reliability (including neighborhood searches), boosts Listing Details performance through server‑side skeletons and cleanup, and fixes UX issues related to OmniSearch, sign‑out navigation, and URL/location‑boundary behavior.

Highlights

  • Improved neighborhood search behavior in global search so users receive more complete and accurate listing results. (GGMI-3604)

  • Improved Listing Details performance by adding server‑side skeletons and removing a legacy CSS file that could cause styling conflicts. (GGMI-3589, GGMI-3591)

  • Stabilized Advanced Search by disabling fields during loading and restoring the previous state once loading completes. (GGMI-3570)

  • Fixed multiple issues that caused messy URLs, lost location boundaries on shared links, and OmniSearch UI inconsistencies. (GGMI-3597, GGMI-3565, GGMI-3564)

Top issues and stability improvements

  • Fixed inconsistent font styling in search dropdown options for a more polished UI. (GGMI-3614)

  • Corrected navigation behavior after user sign‑out so users are routed to the correct destination. (GGMI-3605)

  • Improved global search to return expected results for neighborhood‑based queries that were previously failing or incomplete. (GGMI-3604)

  • Resolved a WordPress app‑password configuration issue. (GGMI-3603)

  • Fixed several OmniSearch UI issues, including icon sizing, placeholder overlap, and weak borders, to improve readability and usability. (GGMI-3597)

  • Removed the legacy Listing Details CSS file single-property-media.css to simplify styling and avoid conflicts. (GGMI-3591)

  • Added server‑side Listing Details skeletons and removed unused HTML after skeleton usage to improve perceived performance and markup cleanliness. (GGMI-3589)

  • Disabled advanced‑search fields while data is loading and restored the previous state after load to prevent inconsistent filter states. (GGMI-3570)

  • Fixed URL behavior where reselecting an already‑selected location reset the URL and re‑appended query parameters. (GGMI-3565)

  • Fixed shared‑URL handling so location boundaries are preserved when opening links with multiple selected locations. (GGMI-3564)