Autocomplete fields broken after upgrade to 4.4.1

[penguintrax]

The field population function in Search Builder is not working either, I've discovered.

Selected:

Contacts in Group(s) = and the field in which the Group Names should display, says 'loading' then shows a blank field.

I checked Firebug's NET panel, and this message was in the Response tab:

{"is_error":1,"0":"error_message","1":"Unable to decode supplied JSON."}

Params tab had the following:

action   getoptions
entity   group_contact
json   {"field":"group","sequential":1}
option   com_civicrm
task   civicrm/ajax/rest

I checked these same tabs for the Autocomplete Search field and they aren't shown.

[Coleman Watts]

@penguintrax I cannot reproduce this on a stock install of CiviCRM in Joomla 2.5. I'm afraid you will have to do some investigating on your own as to why your server is behaving differently.

[penguintrax]

Thanks Coleman - I wasn't able to recreate it on another site.

I'm wondering if I should make a backup of the site and try reinstalling the component.

[Coleman Watts]

Worth a try.

[DamonKirkpatrick]

Having the same issue after the same upgrade.

Apparently there are some permission problems with Joomla that may be deeper than just this problem dealing with the Joomla ACL and the jos_assets table not storing accurate info about com_civicrm permissions.

http://forum.civicrm.org/index.php?topic=29881.0

Some of the issues in the above post refer to ACL problems I was having before the 4.4.1 upgrade.  However, it seems like they might be related.  Does anyone know if the quicksearch relies on a permission that should be in the jos_assets table and isn't? 

I too am super user and should have permission for everything but after the upgrade, I've got some really weird quirks like not being able to delete certain things (an item in a price set, among others). 

I'll keep digging as well and try to find a "known good" jos_assets entry to see if mine is missing something or to find a reference to the QS.

[bmccarthyhp]

I had the same issue after upgrading to 4.4.1 and the error logged was related to the SQL script used for the autocomplete lookups. I don't have the exact error anymore, but it was related to mis-matched table and field collation values. I ran a PHP script to set all table collations to the same.

See this SO post. http://stackoverflow.com/questions/1294117/how-to-change-collation-of-database-table-column. I used the PHP script option.

[DamonKirkpatrick]

Just tried the solution from bmccarthyhp and it worked like a charm on my dev server.  THANKS!

[penguintrax]

The table collations are all UTF8, but the Type is a mix between InnoDB and MyISAM. Could this be related?

[Eileen]

It could indicate a problem - but probably the myisam are non civi or temp-type tables? No core civi tables should be myisam

[penguintrax]

@Eileen

yes, all civi tables are InnoDB

Glad that the proposed fix helped Damon, but it doesn't apply to me, it seems

[DamonKirkpatrick]

@Penguintrax-

Just more info in case it helps...

All of my tables were also utf8.  However, while the vast majority were utf8_general_ci, there were a total of eight or nine tables that were utf8_unicode_ci.  The odd ones were custom tables that had been created fairly recently.  None seemed as though they would be directly related to contact searching but it did fix the problem.

Good luck!

[penguintrax]

I had 3 tables that were utf8_unicode and I changed them to utf8_general

Autocomplete still not working.

[Eileen]

4.4.2 is out so you should upgrade to that in case there is a fix in there

[Donald Lobo]

i just did a quick code check and pretty much all the permanent tables (including custom tables) we create are always:

 ENGINE=InnoDB DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci

So not sure how folks have various combinations of the above (if i had to guess, i suspect DB migrations from various servers). IN general unless you really know what yyou are doing, i would not recommend changing engine type / collation etc

barbara: if 4.4.2 does not fix it and if you have the $$$, might be worth hiring someone from the provider listinf (maybe osseed or web access?) to sort this out.

lobo

[penguintrax]

Thanks Lobo - we have a guy we're working with now that should be able to sort it out if 4.4.2 doesn't fix the issue. I'm hoping this fixes the problem I'm having with paid event registration receipts not being sent, too.