CiviCRM Community Forums (archive)

Hi all

Am I blind, or has the CiviCRM Search block been removed for 3.1?

That's the block where you type Lastname, Firstname and it autocompletes.

I have CiviCRM Quick Add, CiviCRM Create New Record, CiviCRM Language Switcher, CiviCRM Full-text Search and CiviCRM Upcoming Events available, but no CiviCRM Search.

cheers

So it is, thank you.

yes, either of your two options are possibilities and should be easy to accomplish via a drupal block

you might want to check the html/js generated for both cases and adapt them to a drupal block. please share your code once u've developed and tested it

lobo

Right... here we go...

**UPDATE 1 Nov 2011 - a wee bugfix to solve a problem that raised its head with Civi 3.4**

First the disclaimer... this is the first time I've dealth with Ajax, and just about my first go at PHP, so there are likely to be lots of stupid errors, particularly violations of "house style".

Working from our test installation of CiviCRM 3.1.4, the following changes have been made

• CRM/Core/Block.php - added a new CONTACT_SEARCH block type, linked to the new template...
• templates/CRM/Block/ContactSearch.tpl - based on bits of the FullTextSearch and Navigation templates. References Basic search help from the existing file templates/CRM/Contact/Form/Search/basic.hlp

Changes to Block.php

58,59c58
<         FULLTEXT_SEARCH = 7,
<         CONTACT_SEARCH  = 8;
---
>         FULLTEXT_SEARCH = 7;
161,171c160
<                                                                         'region'     => 'left' ),
<                                        self::CONTACT_SEARCH => array(  'template'   => 'ContactSearch.tpl',
<                                                                         'info'       => ts('CiviCRM Contact Search'),
<                                                                         'subject'    => ts('Contact Search'),
<                                                                         'active'     => true,
<                                                                         'cache'      => BLOCK_CACHE_GLOBAL,
<                                                                         'visibility' => 1,
<                                                                         'weight'     => -93,
<                                                                         'status'     => 0,
<                                                                         'pages'      => 'civicrm*',
<                                                                         'region'     => 'left' ),
---
>                                                                         'region'     => 'left' )
311,313d299
<         case self::CONTACT_SEARCH:
<             break;
<

The new ContactSearch block template

Somehow I feel that it is possible to do this without the javascript cut-and-paste... that feels like a maintenance problem in the making.

The other thing that feels wrong is the naming of the input fields - when they were sort_name and contact_id (as in the menu search box) the javascript was picking up the ones in the civicrm menu & that was why autocomplete didn't work. However when the search form is submitted the field needs to be called sort_name. Hence the use of an field ID that differs from the field name - but there must be some way of limiting the scope of the javascript to just a part of the DOM?


<div class="block-crm">
    <form id="id_contact_search_block" onsubmit="getContactSearchURLValue( );" method="post" name="contact_search_block" action="{crmURL p='civicrm/contact/search/basic' h=0 }"/>
        <div style="margin-bottom: 8px;">
        <input type="text" class="form-text" id="contact_search_block_sort_name" name="sort_name" style="width: 10em;"/>
        <input type="hidden" id="contact_search_block_contact_id" value=""/>
        <input type="submit" class="form-submit default" name="_qf_Basic_refresh" value="{ts}Go{/ts}"/>
    </div>
    <a title="{ts}Go to Advanced Search{/ts}" href="{crmURL p="civicrm/contact/search/advanced" h=0 q="reset=1"}">&raquo; {ts}Advanced Search{/ts}</a>
        {help id="id-basic-criteria" file="CRM/Contact/Form/Search/Basic.hlp"}
    </form>
</div>
{literal}
<script type="text/javascript">
function getContactSearchURLValue( )
{
    var contactId =  cj( '#contact_search_block_contact_id' ).val();
    if ( ! contactId || isNaN( contactId ) ) {
        var sortValue = cj( '#contact_search_block_sort_name' ).val();
        contactId = '';
        if ( sortValue ) {
            //using xmlhttprequest check if there is only one contact and redirect to view page
            var dataUrl = {/literal}"{crmURL p='civicrm/ajax/contact' h=0 q='name='}"{literal} + sortValue;

            var response = cj.ajax({
                url: dataUrl,
                async: false
                }).responseText;

            if ( response != '\n' ) {
                contactId = response;
            }
        }
    }

    if ( contactId ) {
        var url = {/literal}"{crmURL p='civicrm/contact/view' h=0 q='reset=1&cid='}"{literal} + contactId;
        document.getElementById('id_contact_search_block').action = url;
    }
}
cj( function() {
    var contactUrl = {/literal}"{crmURL p='civicrm/ajax/contactlist' h=0 }"{literal};

    cj( '#contact_search_block_sort_name' ).autocomplete( contactUrl, {
        width: 200,
        selectFirst: false,
        minChars:2,
        matchContains: true
    }).result(function(event, data, formatted) {
       document.location={/literal}"{crmURL p='civicrm/contact/view' h=0 q='reset=1&cid='}"{literal}+data[1];
       return false;
    });
});
</script>
{/literal}