#66078 closed task (blessed) (fixed)
Remove someecards.com as an oEmbed provider
| Reported by: | johnbillion | Owned by: | whyisjake |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.1.3 |
| Component: | Embeds | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Description
The oEmbed endpoint for someecards.com returns a 404. The provider should be removed.
Examples:
- https://www.someecards.com/v2/oembed/?maxwidth=500&maxheight=750&url=https%3A%2F%2Fwww.someecards.com%2Fbirthday-cards%2Fbirthday-card-create-customize-easy%2F&dnt=1&format=json
- https://www.someecards.com/v2/oembed/?maxwidth=500&maxheight=750&url=https%3A%2F%2Fwww.someecards.com%2Fusercards%2Fviewcard%2F62fec0684aa156b83c35b73c3cdeda63%2F&dnt=1&format=json
- https://www.someecards.com/v2/oembed/?maxwidth=500&maxheight=750&url=https%3A%2F%2Fsome.ly%2Fg75XxU4%2F&dnt=1&format=json
Change History (12)
This ticket was mentioned in PR #13459 on WordPress/wordpress-develop by @suryakantupadhyay.
4 weeks ago
#2
- Keywords has-patch added
The Someecards oEmbed endpoint now returns a 404 response, and card pages no longer advertise an oEmbed discovery link.
This removes the provider patterns for someecards.com and some.ly from the oEmbed allow list and documents Someecards as no longer supported as of WordPress 7.1.1.
Trac ticket: https://core.trac.wordpress.org/ticket/66078
### Use of AI Tools
AI assistance: Yes
Tool(s): OpenAI Codex
Model(s): GPT-5.6 Sol light
Used for: Identifying the relevant code path, final implementation were reviewed and edited by me.
#5
@
4 weeks ago
Ok, thanks for clarifying.
7.1.1 RC is in a couple of hours - punting this to 7.1.2 for continued work since it isn't quite ready.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Confirmed the listed someecards.com oEmbed endpoints return 404.
I also checked the card pages for a discovery link. There is no
<link rel="alternate" type="application/json+oembed">, onlyog:andtwitter:cardmetadata, and both/v2/oembed/and/oembed/return 404.Looks like they dropped oEmbed support in their Next.js rebuild, so removing the provider seems appropriate.