With jquery update 2.0-alpha1 or latest dev, all collapsible fieldsets of the whole drupal page (node/edit, admin/.. ,..) brake, so they can't be clicked anymore.
I got drupal 6.16 and use jquery update for wysywig image upload, but i'm sure that it is jquery upload module which causes the error.

I looked to the source code and saw that drupal doesn't add the "" tags inside the legend-tags, so the collapsible fieldset can't be opened!

My web development bar (firefox plugin) say: "uncaught exception: Syntax error, unrecognized expression: )".
Googleing this error, I also found some jQuery users having this error.

Perhaps this helps?

This could be a duplicate of this issue: http://drupal.org/node/775162 - but i think it isn't..

Comments

Breakerandi’s picture

Sorry, an unwanted link has been created, this is the correct sentence:

I looked to the source code and saw that drupal doesn't add the "< a href="#" >" tags inside the legend-tags, so the collapsible fieldset can't be opened!

Anonymous’s picture

am really glad someone else has this problem because am having the same problem but since no one was talking about it i thought it was only i.

secondly i don't think its a problem with wysywig image upload because i disabled it and still had that problem

Anonymous’s picture

read this post for the solution.................
http://drupal.org/node/507240

Breakerandi’s picture

The patches there don't solve my issue...

aaron’s picture

Version: 6.x-2.0-alpha1 » 6.x-2.x-dev
aaron’s picture

Assigned: Breakerandi » Unassigned
Status: Active » Postponed (maintainer needs more info)

except that they work for me. maybe it's the module(s) you're using? wysywig image upload
and i don't know what jquery upload is; maybe you meant jquery update?

ClearXS’s picture

Not sure adding more to the confusion in-spite to a solution... Have had many problems in this perspective (with several modules conflicting, mostly not even able to find out which ones exactly).

Most problems however were with IE (latest version). Even with IE_CSS Optimization module. But sometimes also with other browsers. Anyway, I'm confused; my cut down site is now working. Documenting every (jQuery, JAVA, AJAX, CSS) step I take and probably will find out several conflicts between those type of modules in future.

It's a weak point of Drupal, where most other professional software works with popups a.s.o., configuring a site to do all this in Drupal, is a bit of a nightmare to me with a lot of obstacles and months of work.

Here my temporary modules list (I have to cut down, some overlap, some conflict, but don't know until I have tried them out):
http://wi-ca.org/Drupal_modules_table_here

Now I will start over after 2 months of problems (even my admin acount had been www open to anyone due to conflicts) to document exactly which such modules I activate and for what purpose:
http://wi-ca.org/Drupal_modules_grouped#JavaScript_AJAX_JQuery

Here the issues I find (just started this, have to add some I've found earlier and others I will find out later):
http://wi-ca.org/Drupal_Java_issues
=> JAVA+AJAX+jQuery issues, I even don't know what is the difference...

In this way I suppose it must be possible to make a module rich complex site with a lot of JavaScript/AJAX/jQuery features with Drupal, but I wouldn't have started this if I 3 years before had known the many problems to get only a bit near those goals...

ronline’s picture

The same prob with 6.x-2.0-alpha. Downgrading to 6.x-1.1fix the issue.
#861460: 6.x-2.x-dev issue

mfer’s picture

Priority: Critical » Normal

@lamachine_fr jQuery Update 1.1 provides the same version of jQuery Drupal core does. If you are not using the uncompressed or minimized options you are just using the version in core.

An error like this would be because a specific module is using JavaScript that is incompatible with jQuery 1.3.2. The key would be to identify the module so a specific issue can be filed against it. A number of features were deprecated in jQuery 1.2.6 and were removed in 1.3.2. This is causing problems with numerous JavaScripts. For these there were better ways put in place. The scripts just need to be updated.

mfer’s picture

Category: bug » support

Filing as a support request. Trying to find the script causing jQuery 1.3.2 to break is not a bug.

mansspams’s picture

Lightbox 2 in my case...

j2b’s picture

... Have not looked through in details, but fix from Russian site http://www.drupal.ru/node/45910 solved issues with Vertical tabs, Fieldsets (collapsing) and remain working Fancybox module. What basically this fix does, it asks to change jquery_update.module code TO the following:

function jquery_update_jquery_path() { 
  $jquery_file = preg_match('/(admin|edit|add)/', request_uri()) ?
  array('none' => JQUERY_ORIGINAL_PATH.'/'.'jquery.js', 'min' => JQUERY_ORIGINAL_PATH.'/'.'jquery.min.js'):
  array('none' => JQUERY_UPDATE_REPLACE_PATH.'/'.'jquery.js', 'min' => JQUERY_UPDATE_REPLACE_PATH.'/'.'jquery.min.js');
 
  return $jquery_file[variable_get('jquery_update_compression_type', 'min')];
}

and

function jquery_update_preprocess_page(&$variables) {
  // Only do this for pages that have JavaScript on them.
  if (!empty($variables['scripts'])) {
 
    // Perform the logic if either jQuery Update's jquery.js is newer than core's.
    if (variable_get('jquery_update_replace', TRUE)) {
      // Get an array of all the JavaScript files loaded by Drupal on this page.
      $scripts = drupal_add_js();
 
      // Replace jquery.js first.
      $new_jquery = array(jquery_update_jquery_path() => $scripts['core']['misc/jquery.js']);
      $scripts['core'] = array_merge($new_jquery, $scripts['core']);
	  if (!preg_match('/(admin|edit|add)/', request_uri())):
		unset($scripts['core']['misc/jquery.js']);
	  endif;
 
      // Loop through each of the required replacements.
      foreach (jquery_update_get_replacements() as $type => $replacements) {
        foreach ($replacements as $find => $replace) {
          // If the file to replace is loaded on this page...
          if (isset($scripts[$type][$find])) {
            // Create a new entry for the replacement file, and unset the original one.
            $replace = JQUERY_UPDATE_REPLACE_PATH .'/'. $replace;
            $scripts[$type][$replace] = $scripts[$type][$find];
            unset($scripts[$type][$find]);
          }
        }
      }
 
      $variables['scripts'] = drupal_get_js('header', $scripts);
    }
  }
}

NOTICE! I am not an js guru and was looking for quick solution. Applied - worked. In nearest days will go through the differences and idea. Probably there could be some side effects too. My be some one with better knowledge can explain or go through the fixes.

j2b’s picture

INFO on my posted code correction!

Probably because of not clearing cache for now I get the following error:

warning: file_get_contents(JQUERY_ORIGINAL_PATH/jquery.js) [function.file-get-contents]: failed to open stream: No such file or directory...

Still have to investigate further!

alexis’s picture

I was also having the broken collapsible fields problem with Drupal 6.x using jQuery Update 6.x-2.x-dev and in my case was related to broken jQuery in Better Select module.

I noticed this in Firebug:

Syntax error, unrecognized expression: [@type="checkbox"]' when calling method

I found the problem could be fixed with this patch (special thanks to markabur). The fix for better select also fixed the collapsible fields problem.

j2b’s picture

I can confirm, that the problem in my case was connected with Better select module as well. I didn't applied a patch. Deployed latest dev version, but these changes are not commited to dev from 2010-Jul-11. By disabling Better select module, everything comes into their places (updated latest jquery update dev 2.x).

ridolfidesigns’s picture

Not sure if anybody had this problem but thought I would document it. I was having the whole collapsible issue too. The problem with mine was that I didn't have:

<?php print $scripts ?>

in my page.tpl.php file. The thing that is strange, is that we had a test server setup and it had that line of code on the theme on the test server but a few days after being on the production server, it seemed to not be in the template file anymore. I hope that helps somebody.

XiaN Vizjereij’s picture

Subscribing

masher’s picture

I too found that disabling Better Select (or disabling jQuery Update) solved the problem.

jruberto’s picture

Disabling jQuery Update to repair broken collapsible fields (for instance, publishing & authoring info on node edit form) does work, but definitely see patch referenced in comment #14 for simple & effective fix to Better Select that allows you to keep both modules enabled.

gumrol’s picture

Same as #11 - I was running Lightbox2 Version 6.x-1.9, when I upgraded to 6.x-1.11, the error disappeared.

david.riches’s picture

Found an issue with compact forms version 1.2.

Disabled the module and fieldsets seems to be working again.

MakeOnlineShop’s picture

Hello,

I have the same problem with an old D5 website, and all solutions here do not work, any idea ?

Thanks for your help.

drupalfever’s picture

I got a solution to this problem that worked for a Drupal 6 website.

I had to insert some JavaScript at the hook_init of one of my modules:


$inline_js = "
$.getScript('/misc/collapse.js', function() {
  $.getScript('/misc/drupal.js', function() {});
});";

drupal_add_js($inline_js, 'inline');

This is the only thing that worked for me.

markhalliwell’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Drupal 6 reached EOL (end-of-life) on February 24, 2016.