This to reduce the load on the server. WP limits REST api posts to 100, and this is the base value used. However, the plugin uses a dynamic approach, based on a square grid, hence when your posts grid number of columns equates the number of rows, the slider will automatically adjust the non-dragged slider button to maintain that square. If you wish to display more posts, reduce your window zoom level (ctrl+mouse scroll on firefox/chrome), this will force the number of columns to expand and therefore the js script will allow more posts to be loaded until the rows match the columns. 9. Multi-post taxonomy query not ranked When you have a custom query to display a set of posts on the front-end which combines multiple post-types under a single taxonomy term, then the plugin needs to be told which post-type to use to rank the results. It will fire a filter which you need to hook, apply_filters('reorderpwc_filter_multiple_post_type', 'ranking_post_type',10,2); function ranking_post_type($type, $wp_query){ //use WP_Query object to figure is this is your query, //then return the post-type the to use to rank the results. //if no type is returned the posts will be ranked by date. return $type; } 10. My posts are not being ranked properly on the front-end There are several reasons why this might happen, 1. You are using a custom query get_posts()... If you are displaying your posts using a custom query with the function get_posts() you should be aware that it sets the attribute 'suppress_filters' to true by default (see the codex page). The ranked order is applied using filters on the query, hence you need to explictly set this attribute to false to get your results ranked properly. 2. Your theme or custom query explictly set the 'orderby' query attribute. ** If your **query explicitly sets the 'orderby' attribute, and the override checkbox is checked (see screenshot #5), then the plugin will override your query and rank the results as per your manual order. However, if you uncheck the ovverride setting (ie override is set to false), your query will be ordered as per the orderby directive. However, you can programmatically override the orderby directive with the following hook should you need finer control, add_filter('rpwc2_allow_custom_sort_orderby_override', 'override_orderby_sorting', 10,5); function override_orderby_sorting($override, $wp_query, $taxonomy, $term_id, $type){ //check this is the correct query if($wp_query....){ $override = true; } return $override; } ** 3. You are displaying a taxonomy archive page. ** If your query is a taxonomy archive query for a given term, then WordPress core query does not specify the post_type by default see this bug). This forces the plugin to seek which post_type is associated with this taxonomy. In the event that you are using this taxonomy to classify multiple post types this will lead to the plugin choosing the first type it encounters with available posts for the queried term, and this may give spurious results. A hook is provided for you to correctly filter the post_type and ensure the right results, add_filter('reorderpwc_filter_multiple_post_type', 'filter_my_ranked_post_type', 10, 4); function filter_my_ranked_post_type($type, $post_types, $taxonomy, $wp_query){ /* String $type post type to filter. * String $post_types post types associated with taxonomy. * String $taxonomy being queried. * WP_Query $wp_query query object. */ if('my-custom-tax' == $taxonomy && in_array('my-custom-post',$post_types)) $type = 'my-custom-post'; return $type; } 11. Programmatically ranking initial post order in admin page. If you are migrating from another plugin in which you have painstakingly sorted your posts, or you need have the intial order of posts based on some other criteria (some date or other meta field value), then you can use the following filter to pass the required rank, add_filter('rpwc2_filter_default_ranking', 'custom_intial_order', 10, 4); function custom_intial_order($ranking, $term_id, $taxonomy, $post_type){ //$ranking an array containing a list of post IDs in their default order. //$term_id the current term being reordered. //$taxonomy the taxonomy to which the term belongs. //$post_type the post type being reordered. //check if this is the correct taxonomy/post type you wish to reorder. if('my-custom-post' != $post_type || 'my-category'!=$taxonomy ) return $ranking; //load you default order programmatically... says as $new_order from your DB $filtered_order = array() foreach($new_order as $post_id){ //check the post ID is actually in the ranking. if(in_array($post_id, $new_order)) filtered_order[]=$post_id; } return $filtered_order; } in version 2.6.1, an additional filter is introduced to allow different post status to appear in the initial rank, add_filter('rpwc2_initial_rank_posts_status', 'allow_draft_in_initial_order',10,3); function allow_draft_in_initial_order($status, $post_type, $term_id){ //allow draft post to be ranked initially. By default $status=array('private','publish','future'). if('post'==$post_type){ $status[]='draft'; } return $status; } this will only affect the posts in the admin dashboard reorder page.