Add oEmbed-based embed shortcode #36
Open
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.
This PR introduces a new shortcode type embed, enabling WordPress oEmbed rendering through Anything Shortcodes.
Included in this PR
Added
Embed_Typeclass to handle[anys type="embed"]Implemented automatic oEmbed resolution using
wp_oembed_get()for supported providers (YouTube, Vimeo, Twitter/X, Instagram, etc.)Added graceful fallback behavior:
fallbackattribute if provided<a>link when oEmbed failsNormalized shortcode attributes through the shared attribute resolver for consistency
Ensured output is returned safely without stripping allowed oEmbed HTML (no
wp_kses_postapplied to iframe output)Let me know if you’d like additional provider-specific handling, URL normalization rules, or stricter sanitization for embed output.