[wp-trac] [WordPress Trac] #14759: Improve the way oEmbed deals with caching

WordPress Trac noreply at wordpress.org
Thu Nov 28 21:57:46 UTC 2013


#14759: Improve the way oEmbed deals with caching
--------------------------+-----------------------------
 Reporter:  Viper007Bond  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Embeds        |     Version:  3.0.1
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------

Comment (by leewillis77):

 Replying to [comment:34 sanchothefat]:
 > Rather than leaving it with no optimal solution would it not at least
 make sense to use transients in so far as it's better than no caching at
 all?

 Not really - transients disappear without notice. Particularly I'm pretty
 sure that transients get cleared specifically on WP upgrade nowadays -
 that would leave some epic re-embedding going on which I imagine wouldn't
 be pretty for sites that embed even reasonable quantities.

 The non-guaranteed persistence of transients makes this unworkable.

 > The only other thing I can think of is that you could register a hidden
 post type, create a single post in it and use that as the fallback post ID
 to cache anything coming from a direct `wp_oembed_get()` call. It seems
 completely crazy but might be the least disruptive.

 I had wondered about child entries in the posts table (In a similar method
 to "attachments"), but not sure it helps us - there's still no expiry
 framework built in.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/14759#comment:36>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list