Skip to content

Comments

Decode URLs when parsing them from content#82

Merged
joehoyle merged 1 commit intomasterfrom
html-decode-src
Aug 9, 2025
Merged

Decode URLs when parsing them from content#82
joehoyle merged 1 commit intomasterfrom
html-decode-src

Conversation

@joehoyle
Copy link
Member

@joehoyle joehoyle commented Aug 9, 2025

WordPress stores URLs in the post content as html entity encoded. Thi means in cases when there are images in the content that have query params, currently our replacements around the use of presign break. In all other cases tachyon_url() expects a clean URL, not a htmlentities applied one, so we make sure to be consistent.

@joehoyle joehoyle requested a review from tomjn August 9, 2025 17:48
WordPress stores URLs in the post content as html entity encoded. Thi means in cases when there are images in the content that have query params, currently our replacements around the use of `presign` break. In all other cases `tachyon_url()` expects a clean URL, not a htmlentities applied one, so we make sure to be consistent.
@joehoyle joehoyle merged commit e41d716 into master Aug 9, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants