Repository navigation
Syncing listings on demand
The queue runs a sync a couple of minutes after a profile is saved. To sync now, to check a silo without waiting, or to run the closing scan, use the WP-CLI command on the site.
Written against v2.5.0.
-
Sync one provider or location:
wp uamswp gbp sync --post=<post id>
A location also covers its published child locations and the providers at them.
-
Or sync every published provider and location:
wp uamswp gbp sync --all
-
Narrow or rehearse the run when needed.
--silo=uams,--silo=arkansas-childrensor--silo=baptist-healthlimits the run to one silo.--dry-runruns every silo that is not Off as a dry run, even a Live silo on the production site. -
Read the output. One line per listing, then a count per action:
<store code> uams dry-run update Dry run, no write made Done: 1 updateThe columns are the store code, silo, mode, action and reason. The command exits
1when any listing ends in review or error, when a create is held back by the daily budget (it prints when creates resume), when Google rate limits the run, when the credentials are missing, when another sync holds the run lock, when--silonames an unknown silo, when there is nothing to sync, when the post is not a published provider or location, when Google refuses the request (Stopped: <message>), or when neither or both of--postand--allis given (Pass exactly one of --post=<id> or --all.). Otherwise it exits0. -
Run the closing scan now, if needed:
wp uamswp gbp sync --orphans --dry-run
It reports every orphaned listing and how many days it has left; without
--dry-run, due listings in a Live silo are closed.--post,--alland--silodo not apply to it.
The command does not use the change check the queue relies on, so it always compares each listing with Google, even when the profile has not changed since its last sync.
-
wp uamswp gbp backfill-idsmatches posts to their listings by store code, then by Google's customer ID, and prints what it would store. Add--applyto store the matches. -
wp uamswp gbp cid-reportlists, asNO LISTINGlines, the providers marked as having listings on Google whose customer IDs match no listing, and, asNO CIDlines, the listings whose customer ID is on no provider or location. It changes nothing.
- Business Profile sync: silos and modes, exclusions, the daily create budget, the activity log and the closing scan.
- Troubleshooting: what each reason in the output means.
Home | Getting started | Guides | Troubleshooting | Reference | Project | README | Repository
Written against v2.5.0 and the unreleased changes on master after it. Edit these pages in docs/wiki/ through a pull request; edits made in the wiki are overwritten by the next publish.
Getting started
Guides
Troubleshooting
Reference
Project