Cardinal Locator version 1.8.0 has been released, adding support for the new cloud-based map styling, adding support for Google’s new advanced markers, fixing bugs and accessibility issues with pagination, improving overall pagination functionality, fixing unpublished locations being added to the coordinates database table, and fixing a newer async loading browser console notice among a handful of other items. The entire PHP codebase was also scanned with PHPStan and all but a few warnings were addressed. Please review the full changelog list below for all the details on the release.
Cloud-based map styling
Google’s new cloud-based map styling doesn’t have to be used at this time, but there are some hints that the current functionality could be deprecated in the future. For example, the current map marker functionality triggers a browser console notice stating that google.maps.Marker will be discontinued at least 12 months from February 21st, 2024. In order to use the advanced markers a Map ID needs to be created and associated with your map, which is how the entire cloud-based styling setup works. However, there is no clear indication that the previous map styling approach using the large JavaScript array that can be generated with services such as Snazzy Maps, will also be deprecated.
If you’re interested in getting started with the new cloud-based map styling make sure to update to version 1.8.0 and then please refer to the 7 steps for using new Google Maps Map ID to style maps via the cloud tutorial article.
Migration of Support tab to Site Health
One minor change you may notice when reviewing the Cardinal Store Locator settings pages, under Settings > Cardinal Locator, is that the Support tab no longer displays. All of the information that was previously displayed in that tab was migrated to the WordPress core Site Health admin page in version 1.8.0 under WordPress dashboard > Tools > Site Health > Info tab.
Taking advantage of the Site Health admin page made a lot more sense than keeping the Support information in the plugin’s Settings page, since there were no settings fields when viewing the tab. The Status tab under Site Health also contains a few checks for common issues related to Google Maps API keys and it will also output any locations that have experienced geocoding issues – for example, when a location has missing or incorrect street address information.
It’s always a good idea to occasionally check the Site Health Status tab after adding a new plugin, updating plugins and themes, adding new custom site functionality, etc.
Version 1.8.0 Changelog
- Added Google Maps API key checks to the admin Site Health Status page.
- Added new Map ID setting under Style Settings tab to support new Map ID Google Maps feature. Please refer to Use Map IDs, Map ID with Styling, and Cloud-based maps styling overview in the Google API docs.
- Added support for new Advanced Markers while maintaining support for the deprecated (not yet discontinued) marker functionality. Map ID setting needs to be set – see previous item.
- Fixed bugs with Pagination and High location count settings enabled.
- Fixed coordinates of unpublished location posts added to custom coordinates database table – only intended for published locations.
- Fixed pagination number count issue after page one, where the incorrect count would display in the location list.
- Fixed new “Google Maps JavaScript API has been loaded directly without loading=async” notice.
- Fixed various WordPress Coding Standards and PHPStan reported issues.
- Improved pagination accessibility and functionality.
- Migrated System Information section in Support Settings tab to the Site Health Info page (Tools > Site Health > Info).
- Removed Support tab from plugin settings page in favor of the core Site Health page (Tools > Site Health).
- Updated Google Maps mapTypeId to new string values (terrain, hybrid, satellite, roadmap).