Description: Adds infinite scrolling support to the front-end blog post view for themes, pulling the next set of posts automatically into view when the reader approaches the bottom of the page.
'requested_type' => 'scroll', // store the original type for use when logic overrides it
65
'footer_widgets' => false, // true | false | sidebar_id | array of sidebar_ids -- last two are checked with is_active_sidebar
66
'container' => 'content', // container html id
67
'wrapper' => true, // true | false | html class
68
'render' => false, // optional function, otherwise the `content` template part will be used
69
'footer' => true, // boolean to enable or disable the infinite footer | string to provide an html id to derive footer width from
70
'footer_callback' => false, // function to be called to render the IS footer, in place of the default
71
'posts_per_page' => false, // int | false to set based on IS type
72
'click_handle' => true, // boolean to enable or disable rendering the click handler div. If type is click and this is false, page must include its own trigger with the HTML ID `infinite-handle`.
73
);
74
75
// Validate settings passed through add_theme_support()
// Check if a legacy `infinite_scroll_has_footer_widgets()` function is defined and override the footer_widgets parameter's value.
176
// Otherwise, if a widget area ID or array of IDs was provided in the footer_widgets parameter, check if any contains any widgets.
177
// It is safe to use `is_active_sidebar()` before the sidebar is registered as this function doesn't check for a sidebar's existence when determining if it contains any widgets.
178
if ( function_exists( 'infinite_scroll_has_footer_widgets' ) ) {
* HTML code to display a checkbox true/false option
376
* for the infinite_scroll setting.
377
*/
378
function infinite_setting_html() {
379
$notice = '<em>' . __( 'We’ve changed this option to a click-to-scroll version for you since you have footer widgets in Appearance → Widgets, or your theme uses click-to-scroll as the default behavior.', 'jetpack' ) . '</em>';
380
381
// If the blog has footer widgets, show a notice instead of the checkbox
382
if ( self::get_settings()->footer_widgets || 'click' == self::get_settings()->requested_type ) {
383
echo '<label>' . $notice . '</label>';
384
} else {
385
echo '<label><input name="infinite_scroll" type="checkbox" value="1" ' . checked( 1, '' !== get_option( self::$option_name_enabled ), false ) . ' /> ' . esc_html__( 'Check to load posts as you scroll. Uncheck to show clickable button to load posts', 'jetpack' ) . '</label>';
386
echo '<p class="description">' . esc_html( sprintf( _n( 'Shows %s post on each load.', 'Shows %s posts on each load.', self::get_settings()->posts_per_page, 'jetpack' ), number_format_i18n( self::get_settings()->posts_per_page ) ) ) . '</p>';
387
}
388
}
389
390
/**
391
* Does the legwork to determine whether the feature is enabled.
add_action( 'wp_footer', array( $this, 'action_wp_footer' ), 21 ); // Core prints footer scripts at priority 20, so we just need to be one later than that
if ( ! $disabled || 'click' == self::get_settings()->type ) {
453
$classes = 'infinite-scroll';
454
455
if ( 'scroll' == self::get_settings()->type )
456
$classes .= ' neverending';
457
}
458
459
return $classes;
460
}
461
462
/**
463
* In case IS is activated on search page, we have to exclude initially loaded posts which match the keyword by title, not the content as they are displayed before content-matching ones
464
*
465
* @uses self::wp_query
466
* @uses self::get_last_post_date
467
* @uses self::has_only_title_matching_posts
468
* @return array
469
*/
470
function get_excluded_posts() {
471
472
$excluded_posts = array();
473
//loop through posts returned by wp_query call
474
foreach( self::wp_query()->get_posts() as $post ) {
// Next, replace any !IE checks. These shouldn't be present since WP's conditional stylesheet implementation doesn't support them, but someone could be _doing_it_wrong().
An exit expression should only be used in rare cases. For example, if you
write a short command line script.
In most cases however, using an exit expression makes the code untestable
and often causes incompatibilities with other libraries. Thus, unless you are
absolutely sure it is required here, we recommend to refactor your code to
avoid its usage.
Loading history...
1179
1180
$page = (int) $_REQUEST['page'];
1181
1182
// Sanitize and set $previousday. Expected format: dd.mm.yy
1183
if ( preg_match( '/^\d{2}\.\d{2}\.\d{2}$/', $_REQUEST['currentday'] ) ) {
// Fire wp_head to ensure that all necessary scripts are enqueued. Output isn't used, but scripts are extracted in self::action_wp_footer.
1245
ob_start();
1246
wp_head();
1247
while ( ob_get_length() ) {
1248
ob_end_clean();
1249
}
1250
1251
$results['type'] = 'success';
1252
1253
// First, try theme's specified rendering handler, either specified via `add_theme_support` or by hooking to this action directly.
1254
ob_start();
1255
/**
1256
* Fires when rendering Infinite Scroll posts.
1257
*
1258
* @module infinite-scroll
1259
*
1260
* @since 2.0.0
1261
*/
1262
do_action( 'infinite_scroll_render' );
1263
$results['html'] = ob_get_clean();
1264
1265
// Fall back if a theme doesn't specify a rendering function. Because themes may hook additional functions to the `infinite_scroll_render` action, `has_action()` is ineffective here.
Automattic /
jetpack
ethitter
An exit expression should only be used in rare cases. For example, if you write a short command line script.
In most cases however, using an
exitexpression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.