Add 9 missing supported Post Types #1915
Merged
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.
Description
This pull request, related to issue #1899, addresses the bug where WP Parse.ly supports only 8 out of 17
@types
for post content in the JSON-LD output. To fix this issue, this PR adds support for the missing@types
to ensure that the WordPress plugin provides complete and accurate JSON-LD data representation.Motivation and context
This change is necessary to align the plugin with Parse.ly's post
@types
and to prevent incomplete data representation.How has this been tested?
I have tested this change by implementing and using the provided filter in #1899 for a couple of the newly supported
@types
. I have validated that, without this change, when usingrepeated_metas
, the post type metadata would returnindex
. With the new types added, it now returnspost
.