CiviCRM Community Forums (archive)

(not sure if this is the correct forum, move as needed)

I'm running civi 4.5 that was upgraded from a minimal 4.4 install on Joomla 2.5. Several issues have accumulated and I'm stuck debugging them (not a webdev guy). In no particular order:

1. Can't assign relationships (anymore?), except through import. The js popup where you select the other party (where you can search or create new contacts) never gets populated. Like it wasn't passed any data. Typing a name out fully doesn't help, nothing is recognized.

2. I can't disable the mailing footer. I've disabled the fact that it's required everywhere, but in the "Headers, Footers, and Automated Messages" page I can't make it non-default. Or disable it also there for that matter. The dialog opens, but nothing changes on save.

3. I can't input tags into tag sets. Works fine on demo (newer joomla there though). Perhaps related to https://issues.civicrm.org/jira/browse/CRM-15717 (yes, subtype of org)? What happens is that the first new tag I enter is fine, gets converted to the gray block version with an X to delete it, but any extra tag gets removed right after entry (there's just enough of a delay to see it getting converted to the grey block). Even just entering one is no good, as after confirmation, nothing gets saved. It's the same through the dedicated dialog and through the inline form on the profile page.

I'm the admin, so 1 and 3 can't be the same as http://forum.civicrm.org/index.php/topic,34971.0.html .

Any pointers on what to do, where and how to inspect further would be great. I know the browser consoles have some js tooling, but that's about it.

The tag set one gives me a series of these in old opera for linux, but it's a css thing:

Unknown pseudo class
  [id='sizzle-1421681075364'] .crm-accordion-header:first

I couldn't find any similar display in the chromium console, but looking at loaded resources showed that one request (from select2) got cancelled (just before a json one succeeded).

=civicrm/ajax/rest&entity=contact&action=getlist&json=%7B%22params%22%3A%7B%22contact_type%22%3A%22Organization%22%7D%2C%22input%22%3A%22e%22%2C%22page_num%22%3A1%7D&_=1421681952839   GET

Is that what you meant? I don't see where I could check for errors directly, save by setting breakpoints.

Thanks. Typing something in the contacts field:

XHR finished loading: GET "http://ebm.si/o/administrator/?option=com_civicrm&task=civicrm/ajax/rest&en…on%22%7D%2C%22input%22%3A%22fox%22%2C%22page_num%22%3A1%7D&_=1421683210622".
jquery-1.11.1.min.js?r=UBlAK:4m.ajaxTransport.send
jquery-1.11.1.min.js?r=UBlAK:4m.extend.ajax
select2.min.js?r=UBlAK:21(anonymous function)

going deeper shows {"is_error":1,"0":"error_message","1":"Unable to decode supplied JSON."}. I can't find where the problematic json is displayed though. The cancelled requests earlier can be ignored, as they were part of the autocompletion routine.

I tried putting "ini_set('display_errors', FALSE);" in both civicrm.settings.php (why two anyway?), but it changed nothing. Did you mean something else?

The decoded json in the query string is displayed fine:
json:{"params":{"contact_type":"Organization"},"input":"fox","page_num":1}

$requestParams['json'] is as above, just with some escapes:
{\"params\":{\"contact_type\":\"Organization\"},\"input\":\"fox\",\"page_num\":1}
json_last_error() returns JSON_ERROR_SYNTAX. Stripping the backslashes with str_replace actually got me further, one ok response (capital s caron there):
{"is_error":0,"version":3,"count":1,"id":0,"values":[{"id":"65924","label":"\u0160entrupert","description":["obcina@aaasentrupert.si"],"icon_class":"Organization"}],"page_num":1,"more_results":false}
That's nicely reproducible also with other data, but the dropdown still isn't getting populated.

Hmm, I wonder if the escapes are a joomla thing, or possibly a misconfigured php environmental variable. The latter theory might explain why random-seeming ajax calls are failing.

Actually, I just disabled all my debug prints around the fix and autocomplete works again. Didn't realize it was offered in so many places. Both tag sets and relationships are fine now.

So basically just the escaping issue remains.