Plugin: ajax-read-more (Used by 15 domains)

When your blog is loaded, all links of this class .more-link (standard wordpress css class for “Read more…”
links) are modified to no longer send the user to that post’s
single page display when clicked. Instead, the WordPress database is queried for that specific post, and all content
after the tag (i.e. only what you need) is returned.
The new content is then immediately displayed to the user with light animation (You can disable animation in plugin options),
inline with the opening content.

• AJAX-read-more uses the jQuery framework already included with WordPress installations.
• This plugin used GET ajax action (not POST, like other plugins), wordpress “template_redirect” action.
• It’s compatible with cache plugins (like Hyper Cache Extended).
• AJAX-read-more: design of progress indicator and other behaviors – by CSS (example – in css/all.css)
• cache-safe script and css url

Check plugin options on options page.

Thanks for debugging to [email protected].

Theme requirements:

• Your theme must generate correct DOM structure:
  (div id=”#content”)
  …
  (div class=”post”)
  …
  (/div)
  (/div)
• Theme must support footer (wp_footer). If not, you can change corresponding option on plugin option page.

For more information, please visit the Sergey S. Betke blog.

ToDo

The next version or later:
* wordpress core integration for cache headers processing???
* optional http cache-control max-age header value and must-revalidate
* just private cache headers, when post has limited access
* check cache plugins support (Hyper Cache Extended): clear cached responces when post modified
* cache-control and Last-Modification headers – to separate plugins
* if-modified http request support (separate plugins)
* the_excerpt optional support
* AJAX-read-more send correct http cache-control headers, and fully support client-side public cache.
* WP 3.3: http://wpdevel.wordpress.com/tag/3-3-dev-notes/
* WP 3.3: replace wp_localize_script() with wp_add_script_before(). wp_localize_script doesn’t support non-string params in WP 3.3+
* WP 3.3: wp_enqueue_script() now works mid-page – insert scripts just into pages when it’t needed