Repository navigation
Avoid duplicate future feed posts - #730
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.
Feed imports now treat scheduled friend posts as existing content when building the remote-post lookup, so future-dated RSS items are not recreated on every refresh before their publish time. URL lookup misses are no longer persisted in the Friends cache, which avoids keeping a stale "not found" result after an item is inserted, and future posts no longer send new-post email notifications before WordPress publishes them.
This addresses feeds that publish entries with future timestamps, such as Terminal Trove, where repeated 15-minute refreshes could create duplicate scheduled posts and duplicate notifications.
Testing:
Changelog
Type
Message
Prevent duplicate imports and notifications for future-dated feed items.
Test this PR in WordPress Playground
You can test this pull request directly in WordPress Playground:
Launch WordPress Playground
This will install and activate the plugin with the changes from this PR.