Problem/Motivation

Installing the 7.x-2.7 release labelled "Stable release covered by the Drupal Security Team" breaks the whole site.

The issue is all the more dangerous since the status and module pages show all modules up-to-date and zero errors. But the entire site is now broken.

Steps to reproduce

Doing a Drush Update kept marking the Alpha release as Unsupported but would not update to a stable version.

Manually updating to the stable version made the drush error go away, but broke all JavaScript on the entire site and for all themes.

Apache restarts, Clearing Caches and Rebuilding Registry etc made no difference.

Proposed resolution

Remove the 7.x-2.7 release from the project page, or at least mark it as not supported.

Remaining tasks

Unknown

User interface changes

Unknown

API changes

Unknown

Data model changes

Unknown

Comments

serenity1 created an issue. See original summary.

mcdruid’s picture

mcdruid commented

As mentioned on the project page, 7.x-2.7 is still the only "stable release" with Security coverage, however it's from 2015. Approximately 75% of the 300k+ sites that use the module are on that branch (presumably that release).

Until recently 7.x-3.0-alpha4 was also marked as supported/recommended but alphas are not "stable" and have no Security team coverage.

The plan is to get a stable release from the 7.x-4.x branch out as soon as possible.

When that happens, we'll mark all previous releases as deprecated / unsupported.

In the meantime, any sites that were using 7.x-3.x releases should test 7.x-4.x (either the dev release or one of the alpha/beta/rc releases as we prepare for the stable release).

grahamvalue’s picture

grahamvalue commented

(updated comment to correct version numbers)

That makes sense.

Here's a little more information on what may have caused the problem.

The installed version kept giving this drush message.
jQuery Update (jquery_update) 7.x-3.0-alpha5 7.x-3.0-alpha5 Installed version not supported

Drush would not automatically update to 7.x-4.0-alpha1

Updating manually to 7.x-2.7 (using drush) made the above drush error go away, but crashed the all JS on the site.

Could this have been due to the backwards update?

Was 7.x-3.0-alpha5 recently deprecated?

In that case, you may be seeing more instances of this issue as people try to update from 7.x-3.0-alpha5 and choose the recommended 7.x-2.7 version instead of 7.x-4.0-alpha1 .

mcdruid’s picture

mcdruid commented

Thanks for the extra info.

Yes, the 7.x-3.0-alpha5 was recently updated to remove the "supported / recommended" status.

It didn't really make sense for an alpha release to have that status, and it was in fact not supported (no updates since 2017).

7.x-4.0-alpha2 has just been released and it'd definitely be best for all sites to test 7.x-4.x and report any problems as that will soon be the only supported branch.

It's unfortunate if drush doesn't make it easy to upgrade from 7.x-3.0-alpha5 to a 7.x-4.x release. If anyone has any recommended methods / workarounds for doing so, perhaps they could share them here.

grahamvalue’s picture

grahamvalue commented

Sure!

With drush, you have to run

drush up jquery_update-7.x-4.0-alpha1

instead of the usual

drush up

But wouldn't it be good to have a note somewhere that one shouldn't update from 7.x-3.0-alpha5 to 7.x-2.7?

Perhaps next to where it says recommended version?

grahamvalue’s picture

grahamvalue commented

This could be important because the stats page reports a good 64,745 or 20% of users on 7.x-3.0; which as you said, was a recommended version until recently.

So all those people could potentially face the same issue when they try to update next.

grahamvalue’s picture

grahamvalue commented

(updating to correct the command)

For updating to the latest alpha version now, please use the following command

drush up jquery_update-7.x-4.0-alpha2

ressa’s picture

ressa
he/him
commented

I was also puzzled that I got an email about running outdated 7.x-3.0-alpha5 on one site, but no notice from another site, where I was running 7.x-2.7 from 2015.

Thanks for sharing that Drush command, I used it to update to the latest 4.0-alpha2 release, and everything works well.

solideogloria’s picture

solideogloria commented

A future-proof command would be the following:

drush up jquery_update-7.x-4.0-rc1
drush up jquery_update

This updates to the latest version, even if a new version has been added after rc1.

mcdruid’s picture

mcdruid commented
Status: Active » Postponed

Marking this as Postponed for now as the plan is to mark 7.x-2.7 as unsupported soon when 7.x-4.x has a stable release (which I think is pretty close).

Thanks for the drush commands that should be useful for anyone that was on a 7.x-3.x release.

mcdruid’s picture

mcdruid commented
Status: Postponed » Fixed

7.x-2.7 has (finally) been marked as unsupported.

Releases from the 7.x-4.x branch are the only Supported versions of the module with coverage from the Drupal Security Team.

7.x-4.1 is the current release.

As noted above, sites that are running older versions should be able to update via drush by running a command like:

$ drush up jquery_update-7.x-4.1

After switching to the 7.x-4.x branch, Drupal / drush's "available updates" functionality should work as usual.

mcdruid’s picture

mcdruid commented

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.