Skip to content
Educational satire No money Priced in time Human review required
BarkBowlTime-commerce dogfooding
Open bowl Take the 2-minute checkup

No-REST fallback

Emergency Beacon

Use this page when richer public REST diagnostics return an internal error. Static beacons prove package files are present; they do not prove activation, seeding, cache state, or release approval.

Static emergency beacon

Check deployed files before debugging REST.

These static files can be opened directly from the deployed theme/plugin directories. They prove package files exist on disk; they do not prove activation, seeding, cache state, or release approval.

Operator order

  1. Open the plugin static JSON beacon directly from wp-content/plugins before trusting REST callbacks.
  2. Open the theme static JSON beacon directly from wp-content/themes to confirm the visual package was replaced.
  3. Open /wp-json/barkbowl/v1/ping only after the static files confirm the expected package is on disk.
  4. Run the seeder twice, save permalinks, and clear caches before comparing dynamic counts.
  5. If static files show v1.29.0 but REST shows an older version or internal error, capture server logs and confirm activation path.

Boundary: this surface does not approve releases, validate credentials, probe private networks, train models, or replace server logs and human review.