WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #14759


Ignore:
Timestamp:
09/01/2010 11:50:18 PM (9 years ago)
Author:
Viper007Bond
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14759 – Description

    v1 v2  
    55Perhaps instead we should use transients to cache this data. That way when embed HTML is updated, posts will eventually be updated too due to expiring caches. I'm thinking a cache time of a week would be good, but with some random +/- to make sure multiple caches don't all expire at once.
    66
    7 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 do this (without a few lines of code) is to edit all of the posts and re-save them to trigger a cache update. That's lame.
     7A 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.
    88
    99Alternate suggestions welcome though.