Repository navigation
fix: keep lexicon data private - #49
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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