Fix: Fatal error on empty @type string in ld+json verification. #403
Conversation
This file contains 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
|
@andremacola thank you, let me see |
ndaidong
added a commit
that referenced
this pull request
Oct 15, 2024
- Merge pr #403 by @andremacola
Merged
|
@andremacola thank you for your quick update. Please double check v8.0.12 I've just released. |
Merged
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.
Urgent: Sorry, but there was a problem passing the @type value in the ld+json verification that was causing a fatal error. Currently, we only check a certain level and configuration of ld+json.
The issue is that some sites unify all entries into a single ld+json script tag and come as an array without the @type at the top level.
This has been resolved in this version. I am working to ensure that this functionality now supports multiple levels of LD Schema context.
I added a test example to avoid this in future releases.
Big sorry for that.