Skip to content

fix: keep lexicon data private - #49

Merged
imantsk merged 2 commits into
betafrom
fix/lexicon-private
Oct 27, 2026
Merged

imantsk merged 2 commits into
betafrom
fix/lexicon-private

Conversation

@imantsk

@imantsk imantsk commented Oct 27, 2026

Copy link
Copy Markdown
Member

Change

Keep Lexicon terms and categories private on the site. Their post type and taxonomy no longer expose public permalinks or standard WordPress REST routes. The admin category picker uses a permission-checked plugin route. Public page settings omit Lexicon terms and descriptions; server translation requests still receive the scoped terms.

For existing installations, a one-time marker clears supported page caches on the first uncached WordPress request after updating. Fresh installations do not clear page caches. External CDN caches may need a separate purge.

Verification

  • A local WordPress fixture returned 404 for a former Lexicon permalink and the standard term and category REST routes. The plugin category route returned 401 signed out and 200 for an authorized admin.
  • A synthetic term and description were absent from visitor page settings and present in server translation settings.
  • PHP suite, 1,471 JavaScript tests, typecheck, PHP and style lint, and build passed.
  • Tests cover authorization, payload privacy, one-time cache purge, fresh activation, downgrade, reactivation, and a failing cache hook.

@imantsk
imantsk merged commit 415ad15 into beta Oct 27, 2026
3 checks passed
@imantsk
imantsk deleted the fix/lexicon-private branch October 27, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant