CiviCRM Community Forums (archive)

Ok i did experience the same problem than you.
So to solve it i did change the code that call the jquery plugin in my drupal theme, and so, all my js is working, even on the civicrm pages.

Do that:

Replace: 
 $(document).ready(function(){
    $("ul.sf-menu").superfish();
  });

by:

  jQuery(document).ready(function($){
    $("ul.sf-menu").superfish();
  });


An it should work now.

Cheers

Olivier

I've encountered this with two sites, running Drupal 6 and CiviCRM 2.2.5 or 2.2.7. It seems like there is something about how CiviCRM instantiates its own copy of jquery that causes subsequent loading of jquery plugins to fail. My Drupal code loads the plugin js file OK, but actually trying to run the function provided by the plugin causes a "is not a function" error in the javascript console. Meanwhile, other inline code using the core jquery methods (like $("#this").hide() in my Drupal code works fine.

Here's an example from the resulting page markup:

Code: [Select]

<script type="text/javascript" src="/sites/all/modules/civicrm/packages/jquery/jquery.js"></script>

... ( several lines lower ) ...

 <script type="text/javascript" src="/misc/jquery.js?n"></script>

... ( several lines lower, getting to my code ) ...

<script type="text/javascript" src="/sites/all/themes/fairvotemn/js/superfish.js?n"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--

  $(document).ready(function(){
    $("ul.sf-menu").superfish();
  });
 
//--><!]]>
</script>

I've tried it with three different jquery plugins (superfish, timers, curveycorners) that all work fine on non-CiviCRM pages, so I don't think the plugin code is the problem here. I've also tried different plugin function invocations like jquery(element).superfish(); and cl(element).superfish();

You can see an example of this problem (for the moment) here:

http://fairvote.reinventingthe.com/civicrm/profile/edit&gid=9&reset=1

Is the CiviCRM invocation of jquery hijacking later plugin loading (meant for the Drupal invocation of jquery)? Can I excise CiviCRM's invocation so my site is not loading jquery twice on some pages?

My solution was to add an IF statement to my js file.

   if($("body").hasClass("section-civicrm")) {
      cj('#my-div').myPlugin();
   } else {
      $('#my-div').myPlugin();
   }

After that everything worked again

Could you tell me which file is the 'js' file you're mentionning ? I searched the various theme, template, libraries, modules, and civicrm files and couldn't find it for sure.

I have several civiCRM functions that do not work (add/remove dashlets to dashboard) unless I disable the jquery_UI module.
However that module is required by other functions on the site (date_popup).
Removing all jquery_ui modules in order to have civiCRM work on the site is not an option, as it would remove functionnality our users rely on and would leaveus open to further incompatibilities when implementing new modules.

As a newcomer, I find this whole thing a huge mess, to be honest.
I can understand that developpers want to use the latest version of some tools, however if the core drupal comes with a given version of Jquery (or other libs for that matter), great care should be taken not to introduce compatibility problems of this kind 

Could you please post the path of the js file to modify, or at the very least the filename ?

which file to modify?  we have the same problem where dashboard js will not work (ie. no drag/drop)

I was bumping into the same problem the other day.

I think the root of the problem is that (a) jQuery's design for multi-version compatibility requires loading <script> elements in a specific order but (b) drupal_add_js (which is used by civicrm.module) does not guarantee <script> order. (This is true in D6. In D7, it can be debated: there is a "weight" option but it seems like it would require on-going twiddling.)

To be more precise, drupal_add_js() is deterministic (given consistent inputs, it will produce consistent outputs), and the order is based on (1) whether the file is included or embedded and (2) the order of drupal_add_js() calls. However, the order of drupal_add_js() calls is hard to predict. For example, if you have two blocks which both depend on <script> elements in the <head>, and if both hook_block implementations call drupal_add_js(), then the order will depend on the visual placement of the two blocks (left/right/top/bottom; first/second/third).

Consequently, the <script> order is predictable for any given configuration (e.g. "out-of-the-box, vanilla Drupal+CiviCRM") but it becomes unpredictable when you allow for different combinations of blocks, modules, themes, etc.

AFAICS, these are the basic approaches:

• Enhance drupal_add_js to provide more robust ordering-guarantees
• Replace drupal_add_js with something that understands jQuery instances+plugins. (I don't think the current Drupal-jQuery modules address this issue... but there are so many of those modules, and they all seemed 50% done when I last looked, so I can't be certain.)
• Remove drupal_add_js; manually build the <script> elements and pass them to drupal_set_html_head.
• Shift the burden to the client with something akin to http://plugins.jquery.com/project/jquery-deps

I really want drupal with working superfish menus to override civi so my integrated site menu system works consistently so disabling jq at drupal level is not a satisfactory solution in my case.