fix(comments): hide pingbacks and trackbacks from the public endpoint - #122
Merged
Conversation
adminCommentConditions has always excluded them, which left GetApprovedCommentsByArticleSlug as the one place they still surfaced. They are automated link notifications rather than anything a reader wrote, and in the migrated WordPress data they are almost entirely SEO spam: 155 rows sourced from domains like weddingdressesideas.com and garciniacambogia-reviews.org, every one of them approved by WordPress. Same predicate as the admin path, so the two agree. Rows stay in the table. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
adminCommentConditionshas excluded pingbacks and trackbacks since the media-library work, which leftGetApprovedCommentsByArticleSlugas the one place they still surfaced. This closes that gap with the same predicate, so the two paths agree.They are automated link notifications rather than anything a reader wrote. In the migrated WordPress data they are also almost entirely SEO spam — 155 rows, all carrying
comment_approved = '1', sourced from:Rows stay in the table; nothing renders them.
Companion to DrexelTriangle/wordpress-etl — the ETL change re-statuses the ~895 spam comments that WordPress itself approved. This PR handles the ones that were never comments to begin with, and needs no reseed to take effect.
go build,go vet, andgo test ./...clean.🤖 Generated with Claude Code