GBRR Location Sync

A small WordPress helper plugin for Reviews and Rating – Google Reviews (g-business-reviews-rating).

What it does

• Automatically syncs all saved Google Business locations once a day via WP-Cron, instead of only the single active/default location the parent plugin refreshes.
• Merges newly fetched reviews into the parent plugin's review store, preserving the row shape the parent expects (checked, order, avatar, etc.) so its "recently checked" guard doesn't re-process every row and re-fetch avatars on each run.
• Fixes the duplicate-default-location bug that can occur after a manual location cycle by re-deriving the default flag on every saved location from the active place ID.
• Adds an admin settings page (Settings → GBRR Sync) showing:
  • Next scheduled sync time
  • Per-location status (rating, review count, last synced, OK/FAIL)
  • A manual "Sync All Locations Now" action
  • A Google Places API connection/key test
  • A rolling sync log (last 500 entries, most recent 50 shown)
• One-time repair routine that backfills missing keys on legacy review rows after upgrading.
• Optional error email notifications: enable in Settings → GBRR Sync and enter one or more addresses (comma-separated) to get a single summary email whenever a sync run has one or more failed locations. Leave the address field blank to use the site's admin email.

Requirements

• WordPress 5.0+
• PHP 7.4+
• Reviews and Rating – Google Reviews plugin active, with an API key and at least one saved location already configured.

Installation

1. Copy gbrr-location-sync.php into wp-content/plugins/gbrr-location-sync/, or upload the release zip (see below) via Plugins → Add New → Upload Plugin.
2. Activate GBRR Location Sync from the WordPress Plugins screen.
3. Visit Settings → GBRR Sync to check status or trigger a manual sync.

Cutting a release

Release zips are built by GitHub Actions (.github/workflows/release.yml), never on a local Windows machine. Bump the Version: header, commit and push, then publish a GitHub release (e.g. gh release create vX.Y.Z) — that triggers the workflow, which reads the version straight from the plugin header, copies just the distributable files into a gbrr-location-sync/ folder, and zips them with Linux's zip on an ubuntu-latest runner, then attaches the result to the release.

The workflow runs on Linux specifically because that's what keeps zip entries forward-slash. Compress-Archive — and naive zipping on Windows generally — embeds literal backslashes in zip entry names instead of the forward slashes the zip format requires. It opens fine locally, but on the Linux hosts WordPress normally runs on, files land with backslashes in their filenames instead of in subfolders, and the plugin fails to install correctly. Building on ubuntu-latest sidesteps the problem entirely rather than working around it — there's no Windows zip tool involved at any point. The workflow also double-checks every zip entry for backslashes and fails the build if it finds any, and fails if the release tag doesn't match the plugin's Version: header.

You can also trigger the workflow manually (workflow_dispatch, or the "Run workflow" button in the Actions tab) to sanity-check a build without publishing a release — it uploads the zip as a workflow artifact either way.

Notes

• This plugin reads its configuration (API key, saved locations, active place ID) directly from the parent plugin's options — it has no settings of its own beyond scheduling.
• API keys are redacted from any logged error messages.

License

GPLv2 or later — see LICENSE.