Autocomplete Google places
| 开发者 | chroudakais |
|---|---|
| 更新时间 | 2026年6月16日 17:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
billing_address_1 and shipping_address_1).
As of version 3.0.0 the front-end script is written in modern, dependency-free vanilla JavaScript (no jQuery required) and the bundled CMB2 settings library has been updated for security.
安装:
- Upload the plugin files to the
/wp-content/plugins/autocomplete-google-placesdirectory, or install the plugin through the WordPress Plugins screen directly. - Activate the plugin through the Plugins screen in WordPress.
- Open the Google Places admin menu (location-pin icon) and enter your Google Places API key.
- Save. Autocomplete is now active on pages that contain the supported address fields.
屏幕截图:
常见问题:
Is this a paid plugin?
No, it is completely free.
Do I need a Google API key?
Yes. As of 3.0.0 there is no built-in fallback key. Create a key in the Google Cloud Console with the Maps JavaScript API and the Places library enabled, then enter it on the Google Places settings page.
Does it still require jQuery?
No. As of 3.0.0 the front-end script is pure vanilla JavaScript and no longer enqueues jQuery.
Which fields are supported?
The standard WooCommerce-style billing and shipping address fields. When an address is selected, address line 1, city, state, postcode and country are filled automatically.
Can I use it on custom form fields?
Yes. In the "Custom fields (Form ID / class)" setting you can target address fields on most forms (Contact Form 7, Gravity Forms, Elementor, and other standard HTML forms) by ID and/or CSS class. Fields added dynamically (Ajax, modals, multi-step forms) are detected automatically.
It does not work on a field built with React or Vue. Why?
Some plugins and themes build their address fields with a JavaScript framework such as React or Vue, where the field value is fully controlled by the framework. On those fields, no external autocomplete (including this one) can attach reliably, because the framework re-renders the input and overrides external changes. This is a limitation of how those frameworks work, not of this plugin. Standard HTML fields are fully supported. Improved support for framework-based fields is planned for a future release.
更新日志:
- New: custom field targeting now works with dynamically added fields. A MutationObserver detects address inputs that appear after page load (React/Ajax modals, multi-step forms, dynamically rendered checkouts) and attaches autocomplete to them automatically.
- Improved: auto-filled values are now written in a way that React and other controlled-input frameworks register correctly, so the filled address is no longer reverted on the next render.
- New: multilingual support. The autocomplete now follows your WordPress site language and region (e.g. fr_FR), so suggestions and the predictions UI appear in the visitor's locale.
- New: "Suggestion type" setting. Choose what Google suggests — street addresses (default), addresses & areas, cities only, regions, or businesses & places.
- New: "Custom fields (Form ID / class)" option. Target address inputs on any form (Contact Form 7, Gravity Forms, custom forms) by ID and/or CSS class, separated by commas. When a suggestion is selected, the matched field is filled with the full street address and nearby city and postcode fields are auto-filled when present. This restores and improves the old "Form ID" targeting from the 1.x line.
- New: choose the autocomplete country scope from the admin settings. Default is Worldwide (works in all of Europe, USA, Canada, Japan and everywhere else); optionally restrict to up to 5 countries (Google's maximum).
- New: redesigned admin settings screen built with React (WordPress' bundled wp.element), including a one-click "Test API key" button that verifies your Google Places key live.
- Changed: replaced the bundled CMB2 library with a lightweight custom settings page (saved via the WordPress Settings API). This removes the vendored library entirely.
- Major release.
- Rewrote the front-end script in modern vanilla JavaScript (ES6); removed the jQuery dependency from the script and its enqueue.
- Security: upgraded the bundled CMB2 library from 2.10.1 to 2.12.0 (addresses CVE-2024-1792) and removed the dead root CMB2 loader.
- Security: removed the hardcoded Google Maps API key fallback; the Maps script now loads only when an API key is configured.
- Security: the Google Maps URL is now built with rawurlencode() and escaped with esc_url_raw().
- Hardening: moved the direct-access guard ahead of all includes, removed unused example files, and added a directory-listing guard to /js.
- Added uninstall cleanup of stored plugin options.
- Compatibility: raised the minimum PHP requirement to 7.4 (required by CMB2 2.12.0); updated "Tested up to".