"uncaught exception: Syntax error, unrecognized expression: #" after 7.x-1.4 update

I am getting this same issue as well, and it just started after upgrading. I am not using jquery update, and except for views and some other essentials, I really don't have any modules installed. Turning off the module fixes the problem. Uninstalling and reinstalling did not help. How can I downgrade to 7.x-1.3? Is that an option?

Here is a list of my .js files as well on my broken page, if that helps

  <script type="text/javascript" src="http://snaped.bluepresley.com/misc/jquery.js?v=1.4.4"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/jquery.once.js?v=1.2"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/drupal.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/ui/jquery.ui.core.min.js?v=1.8.7"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/jquery.ba-bbq.js?v=1.2.1"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/overlay/overlay-parent.js?v=1.0"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/jquery.cookie.js?v=1.0"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/jquery.form.js?v=2.52"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/vertical-tabs.js?v=1.0"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/contextual/contextual.js?v=1.0"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/states.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/form.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/ajax.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/sites/all/modules/resourcefinder/rfform.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/tabledrag.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/textarea.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/sites/all/modules/date/date.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/collapse.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/progress.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/tableheader.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/file/file.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/misc/autocomplete.js?v=7.31"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/filter/filter.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/menu/menu.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/path/path.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/comment/comment-node-form.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/node/node.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/sites/all/modules/field_group/field_group.js?nalvkd"></script>
<script type="text/javascript" src="http://snaped.bluepresley.com/modules/toolbar/toolbar.js?nalvkd"></script>

For those of us that this is affecting, not only are our forms unusable, but all Drupal jquery is non functional, which means that everything javascript related doesn't work on the page where Field Group is used. Upgrading to critical.

This is a major problem now because my client can't edit their site with the Wysiwyg editor as this update has broken all jQuery.

Could we have a fix asap please.

Regards
Geoff

Can anyone give a screenshot with the fieldgroup setup in field UI? We use the 1.4 on our sites, but don't have JS problems.

My Solution

I fixed this (after hours of trying things) by selecting "jquery" in the jQuery and jQuery UI CDN settings on the admin/config/development/jquery_update page. Any of the other settings don't work for me.

On my journey, when I was using the local JS files I was only getting errors when aggregating the JS files. So there seems to be something in the Jquery Update 7.x-2.4 (local) JS that doesn't play well with others. The JS from jQuery may have those bugs removed.

Wonder if this will work for others.
Regards
Geoff

Same problem here after updating jquery to 1.9. Fixed by downgrading to 1.7 with jquery_update. Field_group version used 7.x-1.4
The curious thing was that the error didn't happen on all pages displaying field groups (I use it with collapsed option), but only when field group was following the display of a link field.

I got fieldgroups working by deleting the field group and jquery update modules and re uploading and applying this patch
https://www.drupal.org/node/1995892

Regards
Geoff

I got fieldgroups working by downgrading to field_groups 7.x-1.3 (https://www.drupal.org/node/2097719)

I think this commit causes it - http://cgit.drupalcode.org/field_group/commit/?id=ead74fb26453b8e8784594...

For now I will just stay with
+ Field Groups 1.3
+ Jquery 1.5

I can't reproduce this.
I'm testing with following:
- jquery update 7.x-2.4 (tested 1.9 and 1.5)
- horizontal tabs on a node form

This patch is the only difference between the js version in 1.3 and 1.4. Can you test if reverting this one fixes your problem? https://www.drupal.org/files/issues/field_group-2190425.patch

#6 worked for me ... Was getting this error with the devel_themer module.

Changed jquery_update to jQuery CDN and v. 1.10 - fixed.

I can confirm this problem still exists with:
jQuery update 7.x-2.4 (jQuery Version selected: 1.7, compressed, local)
Field Group 7.x-1.4

Switching the jQuery version (from 1.5 up to 1.10) did not change anything (all caches cleared ;)) and the problem seems to be caused by the drupal form states API for me.

I found out that the problem only exists if there is a collapsible fieldgroup inside a collapsible fielgroup. If the fieldgroup only consists "normal" fields (and no other fieldgroup), everything is working fine.
Problematic structure:

Group "Region" (collapsible, with required fields)
  Group "Region 1" (collapsible, with required fields)
    Field "Booked" (e.g. Textfield, required field)
    ..
  Group "Region 2" (collapsible, with required fields)
    Field "Booked" (e.g. Textfield, required field)
    ..

My workaround was to change the "collapsible"-Attribute in the Subgroup (Region 1, Region 2) to "open":

Group "Region" (collapsible, with required fields)
  Group "Region 1" (OPEN, with required fields)
    Field "Booked" (e.g. Textfield, required field)
    ..
  Group "Region 2" (OPEN, with required fields)
    Field "Booked" (e.g. Textfield, required field)
    ..

Since the Subgroups (Region 1, Region 2) contain a lot of fields, the layout for the user isn't that nice (it would be good to close the subgroups), but this solution works.

Here's my config:
jQuery Update 7.x-2.4 (jQuery Version: 1.7, compressed, local)
Field Group 7.x-1.4

I had this same issue after upgrading from 7.x-1.3 to 7.x-1.5.

If you're having this issue, make sure the ID field is not empty (screenshot attached). It looks like this is a new field that should have been auto-populated in an update hook, but it wasn't. Manually entering an ID solved the problem for me.

This patch fixes the issue for me.

Some field format types were missing from the condition in field_group_update_7007() that determines if the ID setting should be populated.

If you've already upgraded to 7.x-1.4, you'll need to run the update again after applying this patch.

Reviewing this.

This Patch is working fine for me.Making RTBC.

Thx for the patch. I committed it to dev.

Thank you very much, works good. What about a new stable release in some days?

How can updating an old update hook be a solution. What do we expect all the users already on the latest version to do? Do they have to go in their database and manually roll back the schema version and run an update again?

That's not a good experience, couldn't it be done in a new update function?

Hi!

I had this issue too, found this thread and made the above steps:
1. update field_group to dev ( from 7.x-1.5 )
2. UPDATE `system` SET `schema_version`=7006 WHERE `name`='field_group';
3. run update.php

but no luck. In my case a tab type field_group causes the error. 'tab' is missing in $populate_id_setting array, does not this type need ID? If so, why does it cause error?

Patch in #15 works after I manually roll back the schema version and `drush updb` the module. It's been a year since the last comments, though, and no official fix?