ajax call from case create form returns the case dashboard??

[dlats]

I'm trying to get some drupal data to display on the case create form. I use ajax to execute a script that gets the data ok, but firebug tells me the response is the case dashboard page. This would appear to be a security problem. Any solutions?

[demeritcowboy]

You might need to send the key parameter in the call.  See {crmKey} in some existing code in the templates, like CRM/Case/Form/CaseView.tpl  or CRM_Core_Key::get()

But not sure if that's the exact problem here. Assuming you're using 4.0.7 based on the profile.

[dlats]

The site is using 4.4.5.  I'm not calling the api, rather ajax is calling a php script to fetch drupal data. The api just gets civicrm data. I would have to write an api extension and would rather not do that.

[demeritcowboy]

Is this php inside a drupal module or a standalone script?

If it's a standalone script then it might be because of which folder the script is in. Civi might be trying to route the url through its controller.

If it's in a drupal module you probably want to do something like this, where you set up a menu callback and output drupal_json: https://drupal.org/node/305747

[dlats]

It's a standalone script. What folder should it be in?

[demeritcowboy]

Mostly depends on what kind of access you want to allow and your existing folder layout, and what you've already got in your .htaccess and other web config. Try putting it in the web root to start just to see if that fixes it.

[dlats]

That's where it is now.

[demeritcowboy]

Are you able to post some of the code in the script and also the code that makes the ajax call?

[dlats]

If I put the ajax code in a non civicrm page, it works just fine. So I guess it's a permission thing. So, I wrote an api extension that gets the data and the data now shows up on the civicrm page. However, the autocomplete text field that I added to display the data doesn't display anything.  I tried making the autocomplete source local data just for testing and still no display. So civicrm is preventing the autocomplete from displaying???

[Hershel]

  So civicrm is preventing the autocomplete from displaying???

Drupal and CiviCRM often use different versions of jQuery and a different name for the jQuery function. CiviCRM uses cj for example. Check which jQuery toolbox you are using--if it's a CiviCRM field, then you should use the CiviCRM jQuery tools.

[dlats]

I'm using cj on the civicrm case create form. JQueryUI is version 1.9 (according to the page source). Ny code looks like

cj(document).ready(function(){

  cj("#type_dog_name").autocomplete( {
     source: ["Fido","Fideaux","Fidough"]
  });

}); // doc ready

[Hershel]

On the surface, that code looks OK. I have code similar to this on a CiviCRM 4.4.5 site:

Code: [Select]

jQuery(document).ready(function($){
  cj( '#current_employer').autocomplete( '/get_employer_ajax', {
     mustMatch: true
  });
});

and for the outermost block, I used jQuery not cj. Perhaps try that.

Beyond that, I'm not sure--we would probably have to see the page to understand better.

[dlats]

jQuery(document).ready doesn't work either.
The field id="type_dog_name" was added to the case create form via a module implementing hook_civicrm_buildForm() .

$form->add('text', 'type_dog_name', ts(''));

A custom template was modified to include the added field. Indeed the field displays on the case create form.

The js was added using js injector and does appear in the page source.

There is another autocomplete field on the page which works just fine. (std one for contact). The site that I testing on uses civicrm 4.4.3.

[Hershel]

It's almost impossible for us to guess any further at what might be the problem. We would have to see the full page.

[dlats]

I decided to upgrade to 4.4.5. Running the upgrade seemed to work except at the end when I got this error message;

"Queue runner must be configured before execution."

I was getting this error before the upgrade whenever there was db access (ie install extensions). I tried deleting template_c file, clearing the cache and using php 5.3 and 5.5 instead of 5.4. These had no effect, still get the error.

II suspect that this may have something to do with the current autocomplete problem.