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

[WordPress Trac]

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

Comment(by Denis-de-Bernardy):

 Replying to [ticket:14759 Viper007Bond]:
 > A good example of this is Vimeo. Anyone who embedded a Vimeo embed in
 their post before a few weeks ago got `<object>`-based embeds. However now
 Vimeo gives out `<iframe>` based ones. The only way currently to update
 the old embeds to the new HTML (without using a few lines of code) is to
 edit all of the posts and re-save them to trigger a cache update. That's
 painful.

 Alternatively, WP could flush postmeta by key when we know a few that are
 invalid during upgrades. Btw, is it that much of a big deal? I haven't
 tested, but I would assume that Vimeo made sure the old oEmbed code would
 continue to work.

 If you need postmeta to expire, the easy approach is to an expire date
 tied to it in a separate postmeta (much like we do for transients in the
 options table: _$key_expires). Ideally, the stuff key in question gets
 detected and its parent key gets stored accordingly in memcache.

 I'm in agreement with filosofo though: it makes little sense to keep
 refreshing the data.

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