Quicktabs 4.0.1 requires drupal/js_cookie ^1.0, but D11.2.10 isn't compatible with js_cookie 1.0 anymore, only js_cookie 2.0 is supported. It would be gerat if this can be fixed!

CommentFileSizeAuthor
#8 Screenshot 2025-12-16 152620.png34.05 KBkisugiai

Issue fork quicktabs-3563184

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

adam1 created an issue. See original summary.

kisugiai’s picture

kisugiai commented

Well if you have already installed Quick taps the n update js cookie and all is fine

adam1’s picture

adam1 commented

@kisugiai you mean tweaking composer.json, i.e. drupal/js_cookie": "^1.0 || ^2.0 and then just updating with composer update drupal/quicktabs drupal/js_cookie -W?

kisugiai’s picture

kisugiai commented

well @adma1 i have only mad this composer require 'drupal/js_cookie:^2.0' and all was fine

adam1’s picture

adam1 commented

@kisugiai Thanks, but if I run your composer command, I get this error:

Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/js_cookie ^2.0, found drupal/js_cookie[2.0.1-rc1, 2.0.1] but these were not loaded, likely because it conflicts with another require.
Problem 2
- drupal/quicktabs is locked to version 4.0.1 and an update of this package was not requested.
- drupal/quicktabs 4.0.1 requires drupal/js_cookie ^1.0 -> found drupal/js_cookie[1.0.0, 1.0.1, 1.0.2] but it conflicts with your root composer.json require (^2.0).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

kisugiai’s picture

kisugiai commented

Strange because I don't see anything in QT that requires versions its only js cookies
Maybe something is wrong with your installation

adam1’s picture

adam1 commented

I think you're wrong here: the dependency is explicit in Quicktabs’ composer.json (drupal/js_cookie:^1.0), so Composer correctly refuses js_cookie:^2.0. This is reproducible on a clean install.

The proper fix would be to relax the constraint to ^1.0 || ^2.0 and tag a new 4.x release. This keeps BC for Drupal 10 while unblocking Drupal 11.2.x sites.

kisugiai’s picture

kisugiai commented
StatusFileSize
new Screenshot 2025-12-16 152620.png34.05 KB

ah i see well yes i am wrong but my quick look yesterday on the sources i have nothing found like this
hm i wonder why my composer has says nothing and Drupal to.
may be my composer wrong? not sure.

joelpittet made their first commit to this issue’s fork.

joelpittet opened merge request !51

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Active » Fixed

Thanks for reporting it, I have committed it and will make a patch release soon.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

  • joelpittet committed fef8d9e4 on 4.0.x 
    chore: #3563184 Quicktab requires unsupported version of js_cookie

By:...
kisugiai’s picture

kisugiai commented

still update issue
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires drupal/quicktabs ^4.1 -> satisfiable by drupal/quicktabs[4.1.0].
- drupal/quicktabs 4.1.0 requires drupal/js_cookie ^1.0 -> found drupal/js_cookie[1.0.0, 1.0.1, 1.0.2] but it conflicts with your root composer.json require (^2.0).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented

Sorry, haven’t got around to a release I was hoping to knock out a few more issues before a release. Alas, I was busy with work and life.

Maybe you could have a look at one or two in the queue and see if they can help you as well?

kisugiai’s picture

kisugiai commented

well its okay I have updated it manaualy atm ;)

Status: Fixed » Closed (fixed)

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