- ๐ฎ๐ณIndia arisen Goa
Since the patch has been already merged with the dev branch, tried installing the dev release through composer.
Encountered the following issue.
Info from https://repo.packagist.org: #StandWithUkraine ./composer.json has been updated Running composer update drupal/like_and_dislike Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/like_and_dislike dev-1.x requires drupal/core ^8.7.7 || ^9.0 -> found drupal/core[8.7.7, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but the package is fixed to 10.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - drupal/like_and_dislike 1.x-dev is an alias of drupal/like_and_dislike dev-1.x and thus requires it to be installed too. - Root composer.json requires drupal/like_and_dislike 1.x-dev@dev -> satisfiable by drupal/like_and_dislike[1.x-dev (alias of dev-1.x)]. 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. composer [require drupal/like_and_dislike:1.x-dev@dev] failed, composer command failed: exit status 2. stderr=
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 8:04am 14 February 2023 - ๐ฎ๐ณIndia arisen Goa
As mentioned in comment #2 of Project Update Bot, the patch is not fully covering the Drupal 10 compatibility.
Since the patch has already been merged with the development branch submitting a new patch with only the additional changes required.
Changes:
- Composer rules updated as per https://www.drupal.org/node/2514612#s-drupal-9-compatibility โ . Drupal core composer dependency not required.
- Updated the core version requirement.
- Updated the behaviours as per https://www.drupal.org/node/3158256 โ .
Note:
This module is dependent on https://www.drupal.org/project/votingapi โ .
VotingApi module doesnโt have a drupal 10 release yet. Manually installed drupal 10 compatible dev version using
composer require 'drupal/votingapi:3.x-dev@devโ
Manually fixed query issue with voting api module as per https://www.drupal.org/node/3201242 โ
Testing Steps:
- Clone the 8.x-1.x branch of the module.
- Install the voting api module by using composer require 'drupal/votingapi:3.x-dev@devโ.
- Apply the patch.
- Install the module.
- Configure like and dislike feature on any content type.
- There will be error thrown from the voting api module. Fix it as per https://www.drupal.org/node/3201242 โ .
- Clear the cache and review the like and dislike functionality.
P.S. - New developement branch for drupal 10 would be better.
- Status changed to Needs work
over 1 year ago 10:48am 5 April 2023 - ๐ฎ๐ณIndia abhinavk
When I was Installing this module in Drupal 10.0.3, it shows incompatible with 10.0.3.
Attached image.
- Assigned to shivam_tiwari
- Status changed to Needs review
over 1 year ago 11:07am 5 April 2023 - ๐ฎ๐ณIndia abhinavk
I have created a new patch which makes this module D10 compatible and is working fine for me in my local.
I have also run drupal-check for this and as the errors were ignorable, no fixes were added in this patch.
Adding file with drupal-check errors. - @shivam_tiwari opened merge request.
- Issue was unassigned.
- Status changed to RTBC
over 1 year ago 7:40am 7 April 2023 - ๐ฎ๐ณIndia rahul1707
I have tested patch #9 in drupal 9.5.7 and 10.0.3 which applied cleanly and makes module Drupal 10 compatible. Functionality is working as expected. So, moving this to RTBC.
-
adriancid โ
committed 79dbd29b on 8.x-1.x
Issue #3297527 by shivam_tiwari, AbhinavK, Project Update Bot, arisen,...
-
adriancid โ
committed 79dbd29b on 8.x-1.x
- Status changed to Fixed
over 1 year ago 6:22pm 11 April 2023 - Status changed to Active
over 1 year ago 6:23pm 11 April 2023 - ๐บ๐ฆUkraine lobodacyril
@adriancid why you set status to Active? If it's fixed, then the status should be Fixed.
- Status changed to Fixed
over 1 year ago 2:19pm 26 April 2023 Automatically closed - issue fixed for 2 weeks with no activity.