[interchange] Stop looking at Values mv_matchlimit in ncheck

commit dd821de3e57523d2a980819f2d5dbcc15d519c2e
Author: Josh Lavin <[email protected]>
Date:   Mon Aug 22 16:33:54 2016 -0700

    Stop looking at Values mv_matchlimit in ncheck
    
    - the mv_matchlimit Value can be set by the shorthand "ml", which
      many components use. If using such a component on your results
      page, its setting of the matchlimit may take precedence. This is
      not what we want.

 dist/strap/config/ncheck_category.tag |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/dist/strap/config/ncheck_category.tag b/dist/strap/config/ncheck_category.tag
index 1bd94d7..97fec39 100644
--- a/dist/strap/config/ncheck_category.tag
+++ b/dist/strap/config/ncheck_category.tag
@@ -23,7 +23,7 @@ sub ncheck_category {
 		s,::,/,g;
 	}
 	my ($search, $o);
-	my $limit = $::Values->{mv_matchlimit} || $::Variable->{MV_DEFAULT_MATCHLIMIT} || 50;
+	my $limit = $::Variable->{MV_DEFAULT_MATCHLIMIT} || 50;
 	my $more_link = $a_prod_group;
 	if($category && $category !~ /^([0-9]+|Next|Previous)$/ ) {
 		$more_link .= '/' . $a_category;