WP Manifestindependent plugin directory
manifest / integrations / wp-supabase-sync

WP Supabase Sync

Mirrors published WordPress content into a Supabase Postgres table, with diagnostics that name which permission layer is actually broken.

by Claudio Ibe · github.com/0xclaudi0/wp-supabase-sync · website

2stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/0xclaudi0/wp-supabase-sync/archive/refs/heads/main.zip

From the readme

WP Supabase Sync Mirrors WordPress content into a Supabase Postgres table, so a separate frontend — Next.js, a mobile app, anything — can query your content straight from Supabase instead of calling the WordPress REST API. WordPress stays the source of truth and the editing experience. Supabase becomes the fast, queryable read layer, with row level security on it. Not affiliated with or endorsed by Supabase. This plugin connects WordPress to Supabase; "Supabase" is a trademark of Supabase, Inc. Why this exists Plenty of plugins push data somewhere. The thing this one is actually built around is what happens when it breaks. Supabase has two independent permission layers that fail in ways which look identical from the outside, and the single most common support conversation is someone debugging the wrong one. So the diagnostics here do not say "connection failed" — they say which layer refused you, quote what Postgres actually returned, and print the exact SQL that fixes it. The sharpest example: SQLSTATE 42501 means two completely different things. | What Postgres says | What is actually wrong | The fix | |---|---|---| | permission denied for table wpcontent | The GRANT is

Read the full README on GitHub →