So I updated Drupal core to 7.38 today due to the security update. I also updated jquery_update to 7.x-2.6 today after the core update. Doing so caused both of my Drupal sites to slow to a crawl and crash the server. The server logs were filled with scores of "Premature end of script headers" errors.

I managed to get my sites online by deleting /sites/all/modules/jquery_update/ via FTP for both sites. This took about five reboots of the server in order to get in there and delete the files before the server became overloaded again.

So, no more jquery_update for me. The only module I have that was using jquery as a dependency was DrupalChat - and I have been using DrupalChat for several years with jquery_update without issues. So, something changed about jquery_update in this most recent update that causes a major problem, at least with my configuration. I'm on a Dreamhost dedicated server for what it's worth.

CommentFileSizeAuthor
#6 jquery7.2.6issue.png21.78 KBleolandotan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

M2Lanzarin’s picture

M2Lanzarin CreditAttribution: M2Lanzarin commented

Thanks for the post @thermador! I have gotten in the habit of reading the bug reports on any update- had too many problems similar to the one you just experienced- so I won't be updating the module, until I figure out what's going on Thanks again!

beauregard’s picture

beauregard CreditAttribution: beauregard commented

@thermador, thanks for reporting. Since I had in an earlier update of "jquery update" this year the same problem, I checked now first issues before upgrading. This prevented me having the same problem, thanks.

I wonder what the problem caused this time

rudetrue’s picture

rudetrue CreditAttribution: rudetrue commented

I've just installed Drupal 7.38 and jquery update 7.x-2.6, and so far I don't see any issues? I will do more thorough testing soon and post back today if I find any issues. Maybe another module was the cause?

tr-drupal’s picture

tr-drupal CreditAttribution: tr-drupal commented

Could it be, that breadcrumbs are affected by the update? For some reason the second / third level of the bredcrumb is being displayed in black font out of the sudden, while the rest is blue as it always has been. I'm quite sure that installing "jquery update 7.x-2.6" was the only change. Didn't install Drupal 7.38 yet.

darkside1’s picture

darkside1 CreditAttribution: darkside1 commented

I had the same problem,
I was able to get around it by making sure my version was 1.8 (or at least higher than 1.5) :
admin/config/development/jquery_update .... before I updated to 7.x-2.6
did several sites after and no problems

when is the "jQuery update" required , I didn't have it installed on a site I updated to core 3.8 and had no problems either

I did note that wile it was broken my "Administration menu 7.x-3.0-rc5 " was missing

leolandotan’s picture

leolandotan CreditAttribution: leolandotan as a volunteer commented
FileSize
jquery7.2.6issue.png21.78 KB

I also experienced this issue. I updated core to 7.38 and included JQuery Update since it's also a security update.

I provided a screenshot of the error.

Is there a way that I can revert back safely to 7.x-2.4?

Thanks!

paulraines’s picture

paulraines CreditAttribution: paulraines commented

For me after the update my pages using collapsibles via the collapse.js stopped working. Actually it was weirder than that. The first load of the page after a cache clear worked fine, but any later load the page showed a non-working page.

When I compared page source between first page load after clear and second load, I notice the

collapse.js line was moved much further down so below the jquery script lines. So my guess is precedence was changing between cached and non-cached versions of the page and something in the jquery update now conflicts with collapse.js. I then went into the jquery_update module config and changed it from using 1.10 to using included drupal version. The problem then went away.
leolandotan’s picture

leolandotan CreditAttribution: leolandotan as a volunteer commented

Hi, I finally figured out my issue. It's not related with the security update but based on the error message I got, I changed the allow_url_fopen value in php.ini from Off to On.

shgrettenberg’s picture

shgrettenberg CreditAttribution: shgrettenberg commented

We've had issues with JQuery update for quite some time. Customers think their site is out of date, because they do not have the latest version installed. But the installation bumps Jquery to a version that is incompatible with site elements - for instance for one client it was their rotating picture block on the homepage. The module should come with a warning! For quite a few sites, updating JQuery breaks the site. Extreme caution should be used. This kind of landmine to users should have a warning, or not be seen as a critical update in Drupal.

jantoine’s picture

jantoine CreditAttribution: jantoine as a volunteer commented

I am having a similar issue but have found that disabling all options on the performance page resolves the issue, so for me it seems to be an aggregation issue. Can anyone else confirm that disabling all options on the performance page fixes their issue?

EDIT: My issue was due to my file systems tmp folder being misconfigured.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Status: Active » Closed (outdated)