Merged
Conversation
✅ WordPress Plugin Check Report
📊 ReportAll checks passed! No errors or warnings found. 🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check |
nklhtv
approved these changes
Feb 28, 2026
galbus
deleted the
s-7904-el-libero-404-not-found-errors-weve-supplied-rest-api
branch
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
2 participants
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.
The
onTrashPost()andonDeletePost()hooks had no guard, so they fired for every post type. For revisions/sitemaps/auto-drafts that have no BeyondWords content,deleteAudio()fell back to using the WordPress post ID as the content ID — which doesn't exist in the BeyondWords API, and 404d.Fix:
hasContent()guard ononTrashPost()/onDeletePost()now skips posts without BeyondWords content.