One solution to javascript or jquery problems

[petednz]

After finding that post upgrade to 3.4.6 we could not expand any accordions in Adv Search nor access eg Settings on Manage Contribution Pages with problems identified via 'inspect element' as eg
Uncaught ReferenceError: cj is not defined

on IRC kurund suggested following which proved to be the solution in our case

- regarding jquery failures, if you have jquery_update module, try disabling it ..

[Eileen]

http://issues.civicrm.org/jira/browse/CRM-8774

[Kurund Jalmi]

Peter,

Here is the patch for fixing issues with jquery_update module: https://fisheye2.atlassian.com/changelog/CiviCRM?cs=36592

Once you apply the patch you will need to disable / re-enable CiviCRM module.

Do let me know if it works for you.

Thanks
Kurund

[CiviTeacher.com]

this patch fixed the issue for me.   folks out there: either apply the patch or replace the civicrm.install and civicrm.module files with the complete versions from the patch above.

[jhood]

I just recently upgraded from 3.1 and ran into this same issue. Your advise to overwrite civicrm.install and civicrm.module with the patched versions linked to above worked for me!

If it helps anyone, on Drupal those two files are in the sites/all/modules/civicrm/drupal folder

Thanks!

[Upperholme]

Is this still an issue, or has this solution been incorporated into a stable release?

I ask because I've just upgraded a Drupal site to CiviCRM 4.1.2 from 3.3, and had to disable jQuery Update for it to work.

[Hershel]

I just upgraded a Drupal 6 multisite from CiviCRM 3 to CiviCRM 4.1.3 the jQuery Update module indeed still causes the cj is not defined error.

EDIT: My mistake. Seems that running the Drupal database upgrader fixes this problem.

[demeritcowboy]

Does the line

Code: [Select]

if ($config->userFramework == 'Drupal') {near the bottom of CRM/Upgrade/Incremental/php/ThreeFour.php also need to include a check for framework = 'Drupal6' ?

I did an upgrade on Drupal 6 from 3.3 to 4.2 and the weight didn't get updated. Manually updating it didn't solve my specific problem, but I stumbled onto that code while looking into it.

In my case CRM-8774 causes custom js added during a hook to now get added AFTER the noconflict call, and changing the weight doesn't help because the hook always runs later. Changing *some* of the cj's to $'s in the custom code seems to fix it but why only *some* confuses me - will have to play with that *some* more.

[demeritcowboy]

Just for anyone looking for this where your custom javascript inserted during a hook is no longer working because of the new placement of noconflict, it's probably because of a reference to the jQuery object directly in your javascript. Changing just that part to "cj" seems to work, and then you can leave any $ signs and other references to cj as is.

Also updated the upgrade code to check for Drupal6. (http://issues.civicrm.org/jira/browse/CRM-10958)