Andrew

I’ve tried different calculations for the offset using found posts in the calculation, but I can’t work it out.

I use the WordPress custom loop to it’s fullest using $the_query = new WP_Query( $loop_args );
So I will try and push infinite scroll to its limits 🙂 It is all working fine though except for that incorrect offset for my meta_query rating range. The date_query (which is similar to the meta_query parameter) which shows posts between a date range is working with the correct offset.

I’m currently just using the infinite_scroll_query_args filter to get the correct offset for the rating range:

// show events with at least a rating of 1
function hp_jetpack_infinite_scroll_query_args( $args ) {
        $args['post_type'] = 'event';
	$args['meta_query'] = array(
	       array(
			'key' 		=> 'rating_count',
			'value' 	=> 1,
			'compare' 	=> '>=',
		)
	);	
 
    return $args;
}

add_filter( 'infinite_scroll_query_args', 'hp_jetpack_infinite_scroll_query_args', 100 );

Once I get that rating range working correctly, my full infinite scroll filter looks like this:

function hp_jetpack_infinite_scroll_query_args( $args ) {

	// defaults
	$args['post_type'] = 'event';
	$args['orderby'] = 'date';
	$args['order']   = 'DESC';
			
	// User control loop Filters
	if( hp_is_url_query_string() ) {

		// Type (post type)
		if( hp_query_string( 'type' ) ) {
			$args['post_type'] = hp_get_sanitized_url_query_string_type_value();
		}
			
		// Search term
		if( hp_query_string( 's' ) ) {
			$args['s'] = get_search_query();
		}
		
		// Event category (taxonomy)
		if( hp_query_string( 'event_category' ) ) {
			$args['event_category'] = hp_get_sanitized_url_query_string_event_category_value();
		}

		// Order by date posted
		if( hp_query_string( 'orderby', 'newest' ) ) {	
			$args['orderby'] = 'date';
			$args['order']   = 'DESC';
			
			// bug fix
			$paged = (int)$_POST['page'] + 1;
			$args['paged'] = $paged;
		}
		
		// Order by comment count
		if( hp_query_string( 'orderby', 'comment_count' ) ) {	
			$args['orderby'] = 'comment_count';
			$args['order']   = 'DESC';
			
			// bug fix
			$paged = (int)$_POST['page'] + 1;
			$args['paged'] = $paged;
		}
		
		// Order by Rating
		if( hp_query_string( 'orderby', 'rating' ) ) {	
			$args['meta_key'] = 'rating_count';
			$args['orderby'] = 'meta_value_num';
			$args['order']   = 'DESC';
			
			// bug fix
			$paged = (int)$_POST['page'] + 1;
			$args['paged'] = $paged;
		}
		
		// Order by view count
		if( hp_query_string( 'orderby', 'view_count' ) ) {	
			$args['meta_key'] = 'view_count';
			$args['orderby'] = 'meta_value_num';
			$args['order']   = 'DESC';
			
			// bug fix
			$paged = (int)$_POST['page'] + 1;
			$args['paged'] = $paged;
		}

		// Date range
		if( hp_query_string( 'after' ) || hp_query_string( 'before' ) ) {
			$args['date_query'] = array(
				array(
					'after'     => hp_get_sanitized_url_query_string_after_value(),
					'before'	=> hp_get_sanitized_url_query_string_before_value(),
				)
			);
		}

		// rating range - Bug, incorrect offset
		if( hp_query_string( 'rating' ) ) {
			$args['meta_query'] = array(
				array(
					'key' 		=> 'rating_count',
					'value' 	=> hp_get_sanitized_url_query_string_rating_value(),
					'compare' 	=> '>=',
				)
			);
		}		
	}
 
    return $args;
}
add_filter( 'infinite_scroll_query_args', 'hp_jetpack_infinite_scroll_query_args', 100 );

I now know there is at least 2 things that is affecting the offset of my meta_query rating range:

1. the posts_per_page set in admin. If I set this to 1 post per page, there will be no offset which means I can use the same bug fix used on the orderby parameter.

2. The other thing affecting the offset is the total posts of the post type (not the found posts).
So if the wp_count_posts( 'your_post_type' )->publish is much higher than the: $wp-query->found_posts; There will be no offset, which means I can add the same bug fix used on the orderby parameter.

I don’t know if you can work out a fix for this based on this information.

• This reply was modified 9 years, 5 months ago by Andrew.

Thanks.

Looks like this is the best option for it:

<ul class="pagination">					
	<li class="nav-previous"><?php previous_posts_link( 'Previous posts' ); ?></li>
	<li class="nav-next"><?php next_posts_link( 'Next posts', $the_query->max_num_pages ); ?></li>
</ul>

• This reply was modified 9 years, 7 months ago by Andrew.

I’ve had a look at https://github.com/r-a-y/buddypress-followers/wiki/Create-your-own-follow-activity-loop

if ( bp_has_activities( array(
// change the user ID below to whatever
‘user_id’ => bp_get_following_ids( ‘user_id=3’ )
) ) ) :

How would I write this so it displays activity items from all users that a user is following?

I read somewhere, if an admin panel is compromised a hacker can upload a plugin with malicious code. So adding DISALLOW_FILE_MODS prevents that.

I don’t want to disable the update notifications, I want to keep them to notify me when new updates are available, I am just making sure that define( ‘DISALLOW_FILE_MODS’, true ); doesn’t disable the update notifications.

That’s understandable, perhaps this question was more appropriate for another forum if it is more of a general internet question – but I was unsure.

“You have to buy a cert for each domain.”

So, (apologise if this seems an obvious question to you) if a user maps a domain, they won’t be able to access the admin/login securely? But this was why I asked if it is possible to force the admin side to use the subdomain instead of the mapped domain so the user will at least benefit from my wildcard cert in the admin. (if that makes sense).

I bought a wildcard SSL certificate from my host:
http://www.siteground.com/ssl_certificates.htm

The actual name of it on my account says ‘Alpha SSL Certificate’, so I believe it was a resell of this one:
http://www.alphassl.com/ssl-certificates/wildcard-ssl.html