Yoast SEO 28.3 — docs(indexables): Document new wpseo_indexable_indexing_failed action - #422
Open
claude[bot] wants to merge 1 commit into
Open
Yoast SEO 28.3 — docs(indexables): Document new wpseo_indexable_indexing_failed action#422claude[bot] wants to merge 1 commit into
claude[bot] wants to merge 1 commit into
Conversation
Yoast SEO 28.3-RC2 adds a new action that fires when an indexable cannot be built due to an unexpected error, letting third parties observe and forward build failures.
claude
Bot
added
rc-doc-sync
Deploying yoast-developer with
|
| Latest commit: |
88ba950
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f6fc258a.yoast-developer.pages.dev |
| Branch Preview URL: | https://rc-sync-wordpress-seo-28-3-r-ypgq.yoast-developer.pages.dev |
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.
RC docs sync — 28.3-RC2
Product: wordpress-seo
Area: indexables
Source evidence:
src/builders/indexable-builder.php:5701(diff line): newdo_action('wpseo_indexable_indexing_failed', $object_id, $object_type, $object_sub_type, $exception)call fired from therebuild_for_object()catch-allThrowablehandlersrc/exceptions/indexable/indexing-failed-exception.php(new file):Indexing_Failed_Exceptionwraps the failing object's identity (id, type, sub-type) and passes it up the call stack; the error message is also shown in the SEO data optimization error report (changelog 28.3)Changes in this PR
docs/features/indexables/filters.md: adds a new "Observing indexing failures" section documenting thewpseo_indexable_indexing_failedaction, with parameter table and a completeadd_action()exampleVerification
yarn buildpasses locally in this workflow.yarn lintclean for files touched by this PR.Reviewer notes
$exceptionparameter is the originalThrowable(not the wrappingIndexing_Failed_Exception), so callers get the root cause directly.$object_idisnullfor id-less object types such ashome-page,system-page,date-archive, andpost-type-archive. The example'serror_logcall handles this correctly withwp_json_encode.Sibling PRs from this RC
schemamap.xmlsite-root URLwpseo_disable_xml_sitemap_cache_primingfilterAuthored by the RC docs-sync agent. Not auto-merged — requires human review. Run: https://github.com/Yoast/developer/actions/runs/30983367949