CiviCRM Community Forums (archive)

This issue came up in CiviCRM 3.0.1 on Joomla 1.5.14

I composed a custom search component following the instructions in the documentation:

http://wiki.civicrm.org/confluence/display/CRMDOC/Custom+Search+Components

It worked fine except that it returned all of the data in the data set in a single page, 120 rows instead of the 50 I expected. Changing the Rows per Page value did not make any difference.  The same behaviour occurred with a couple of the Custom Searches in the distribution (I think ContributionAggregate and ...) except that they returned thousands of rows and locked up my browser. I can't find anything on this issue in the Forums. Is it a feature or a bug? I tried looking through the code of the various Custom Searches without being able to figure out how/where to apply a fix. Any pointers would be appreciated.

Cliff

Actually, the demo link did not tell me anything. However, I had a look at the source of the Proximity search and the Base search that it extends and figured out that the lines that were missing were:

        if ( $rowcount > 0 && $offset >= 0 ) {
            $sql .= " LIMIT $offset, $rowcount ";
        }
Just before
        return $sql;

My custom search behaves properly now. I think it would be a good idea to put these lines into the ContributionAggregate and ContribSYBNT searches (and perhaps others) and in the example in the documentation.

Thanks for the pointer.

Cliff

Hi, I am new here, but currently also fighting to get my first custom search through.

If you will be updating the wiki page, it'd be great if there could be another setup link added to the green box below "Register your custom search component" - the current goes to an unrelated page if using non-clean URLS.
Out of my head, I think it's the same except that the questionmark has to be replaced with a slash (/)

i.e.
...civicrm/admin/options/custom_search/group=custom_search&reset=1

That would sure save future developers some time:)
Thanks, Boris

I added a few lines at the bottom of the custom search documentation under Testing. It looks like part of the original rather than a tip, but it makes the point without needing to be changed when the example custom searches get updated in 3.1.

Cliff