[wp-trac] Re: [WordPress Trac] #1595: Post Content Prerendering

[WordPress Trac]

#1595: Post Content Prerendering
--------------------------------------+-------------------------------------
 Reporter:  markjaquith               |        Owner:  markjaquith
     Type:  enhancement               |       Status:  reopened   
 Priority:  normal                    |    Milestone:  2.2        
Component:  Optimization              |      Version:  2.1.2      
 Severity:  normal                    |   Resolution:             
 Keywords:  2nd-opinion dev-feedback  |  
--------------------------------------+-------------------------------------
Comment (by markjaquith):

 My original suggestion was that we keep the_content running live for 100%
 backwards compat, and implement a new the_content_filtered hook that'll
 run on the pre-filtered content (i.e. after the_content).  That way plugin
 authors can update at their leisure and once they do, the full speed
 benefits will be realized.

 the other option is making the new hook the "live" option that is run
 every time.  This will break any plugins that need to run live (few do),
 but it'd give us the maximum immediate speed boost.

 We'd also need to make sure that the prerendered content expires whenever
 plugins are enabled or disabled.  We'd want to functionize that so that
 other plugins could call it.  For instance, say you have a plugin
 activated that alters the_content, and you change an option in that
 plugin.  You'd want the prerendered content to expire so it could be
 updated.

 We might eventually have Manage > Cache with built-in HTML output cache
 management that would allow you to manually flush the HTML + content
 prerendering caches.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/1595#comment:8>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software