- Issue created by @mably
- First commit to issue fork.
- Status changed to Needs review
over 1 year ago 9:05am 29 June 2023 - 🇮🇳India dineshkumarbollu
Hi
I created patch for D10 version please review and also i am attaching D10 report.
Thanks.
- Status changed to RTBC
over 1 year ago 8:24pm 29 June 2023 - 🇫🇷France mably
Patched version works perfectly fine on a Drupal 10.1 instance.
- 🇪🇸Spain psf_ Huelva
Thx for the patch,
Please, could you use the Merge Request instead of the patch file?
- @dineshkumarbollu opened merge request.
- 🇮🇳India dineshkumarbollu
Hi
I created MR! for this issue please review
Thanks
-
psf_ →
committed c446771d on 1.x authored by
dineshkumarbollu →
Issue #3371110 by dineshkumarbollu: Add Drupal 10 compatibility
-
psf_ →
committed c446771d on 1.x authored by
dineshkumarbollu →
- Status changed to Fixed
over 1 year ago 8:32am 30 June 2023 - 🇪🇸Spain psf_ Huelva
Please, if someone can try the dev branch I can add a new version.
- 🇫🇷France mably
There is a trailing colon behind
drupal/key:
in the require section, it should be removed:"require": { "drupal/core": "^8.7.7 || ^9 || ^10", "drupal/key:": "^1.14" },
We get this error when installing via composer:
Problem 1 - drupal/fuzzy_key_provider dev-1.x requires drupal/key: ^1.14 -> could not be found, it looks like its name is invalid, ":" is not allowed in package names. - drupal/fuzzy_key_provider 1.x-dev is an alias of drupal/fuzzy_key_provider dev-1.x and thus requires it to be installed too. - Root composer.json requires drupal/fuzzy_key_provider 1.x-dev@dev -> satisfiable by drupal/fuzzy_key_provider[1.x-dev (alias of dev-1.x)].
- @mably opened merge request.
- Status changed to RTBC
over 1 year ago 1:47pm 30 June 2023 - Status changed to Needs review
over 1 year ago 9:00am 2 July 2023 - 🇪🇸Spain psf_ Huelva
Hi, thx. I merged the fix, please, mark it how fixed if is ok : )
- Status changed to Fixed
over 1 year ago 10:56am 2 July 2023 - 🇫🇷France mably
Was able to install it successfully using composer on both D9 and D10 instances.
Can confirm that it works fine on both platforms.
Automatically closed - issue fixed for 2 weeks with no activity.