| 开发者 | tomawesome |
|---|---|
| 更新时间 | 2026年11月1日 03:52 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[tomawesome_reviews id="123"]tomawesome-review-widgets directory into /wp-content/plugins/.No. Activation does not contact Google or download reviews. You must configure your own Google credentials, create or import a source, and synchronize that source before a widget can display anything.
Use Places when five Google-selected reviews are enough. It still requires Google Cloud, billing, Places API (New), an API key, and a Place ID, but it avoids Business Profile project approval and OAuth. Use the managed Business Profile path only when the connected Google account owns or manages the location and you need the complete review list, multiple managed locations, or Healthcare Privacy Mode.
There is no guaranteed timeline. The hands-on configuration requires multiple Google Cloud and OAuth steps, and Google separately reviews the Basic API Access application. Approval may take days or longer. TomAwesome cannot submit, approve, check, or accelerate that application for you.
No. Every site operator creates and controls their own Google Cloud project and credentials. Do not share one approved project or its credentials across unrelated businesses without confirming Google's current requirements.
Yes. Widgets are unlimited and each has its own source, layout, filters, responsive columns, and display controls.
Yes. One connected Google account can import multiple managed Business Profile locations. You may also configure multiple public Places sources.
The Places API currently returns at most five reviews selected by Google. Use the Business Profile connection for a complete review list from a business you manage.
Google's Places policies require a clear description of review selection, filtering, and ordering, along with Google Maps attribution, available author attribution, returned provider credit, and direct access to each individual source review. The plugin places the concise notice beside the Google Maps attribution in the footer and updates it when the widget's count, minimum rating, written-text requirement, or order changes. These elements are tied to the selected source type and are not optional styling controls. Do not hide them with Custom CSS. Open Review Widgets > Getting Started > Public Places for the full explanation and current policy link.
First import and synchronize the managed location as a new source; do not convert the existing Places source. Edit the widget, select the new managed Business Profile source, and update it. The Places selection notice, Places-specific Google Maps attribution, returned provider credit, and individual Places-review links disappear automatically on the next page load. Reviewer photos become optional, Healthcare Privacy Mode becomes available, and the managed source can retrieve the complete paginated review list.
No. Current Google Maps policies require Places reviews to retain available author attribution and an individual source link. Select a managed Business Profile source before enabling the privacy workflow.
No plugin can certify an organization's HIPAA compliance. The mode enforces privacy-oriented display restrictions and a manual approval workflow, but the site owner must determine whether each use is lawful and consistent with Google terms.
No. There is no TomAwesome proxy, analytics service, telemetry, advertising service, or paid account. Configured API requests go directly between the WordPress site and Google.
WordPress schedules a daily synchronization. Administrators can also synchronize a source manually. WordPress Cron depends on site traffic; sites with low traffic may use a real server cron to call wp-cron.php.
No more than 30 days. Successful synchronizations renew the local performance cache. Expired content is removed even after a failed synchronization.
The shortcode renders only eligible, unexpired reviews. Google content is stored for no more than 30 days. If daily synchronization repeatedly fails, the stored reviews eventually expire and the public shortcode intentionally returns no review markup. Open the selected Review Source, check Last successful sync and Last error, then select Synchronize now. Do not recreate the page, widget, or shortcode before checking source health.
When the connection previously worked, this commonly means Google rejected the saved OAuth refresh token. External OAuth apps left in Testing generally receive refresh tokens that expire after seven days for this scope. Complete Google Auth Platform > Branding, publish the app under Audience according to Google's current requirements, then disconnect and reconnect Google in WordPress. Synchronize the source again after reconnecting. Publishing removes Testing mode's seven-day limitation, but Google can still revoke authorization for other reasons.
A WordPress page cache or hosting/CDN cache may still contain HTML generated while no valid reviews were available. Purge all page caches after the successful synchronization. With WP Super Cache, open Settings > WP Super Cache and select Delete Cache. Then check the normal page URL while logged out or in a private browser window. The complete error-by-error checklist is in the Troubleshooting Guide.
By default, saved configuration and content remain to prevent accidental data loss. Enable “Delete plugin settings...” under Review Widgets > Google Connection before uninstalling if you want all plugin data removed.