Looks like the module has no deprecated code usages, so we just need to mark it as compatible with D9.

So, add core_version_requirement: ^8 || ^9 to all info.yml file as per the definition https://www.drupal.org/node/3070687.

Comments

Sahana _N created an issue. See original summary.

sahana _n’s picture

Status: Active » Needs review
StatusFileSize
new398 bytes

Please review the patch.

Rangaswini’s picture

Assigned: Unassigned » Rangaswini
Status: Needs review » Needs work
Rangaswini’s picture

Assigned: Rangaswini » Unassigned
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new373 bytes
new119.65 KB
naresh_bavaskar’s picture

Assigned: Unassigned » naresh_bavaskar
naresh_bavaskar’s picture

Assigned: naresh_bavaskar » Unassigned
Status: Needs review » Reviewed & tested by the community

patch looks fine, all files code having drupal 9 compatible.

kishor_kolekar’s picture

Issue tags: +Drupal 9 porting dayDrupal 9 readinessDrupal 9 compatibility
kishor_kolekar’s picture

Status: Reviewed & tested by the community » Needs work
Issue tags: -Drupal 9 porting dayDrupal 9 readinessDrupal 9 compatibility +Drupal 9 porting day, +Drupal 9 readiness, +Drupal 9 compatibility
StatusFileSize
new373 bytes

Patch name should follow the pattern [description]-[issue-number]-[comment-number].patch

Fixing the patch name!!

hardik_patel_12’s picture

Status: Needs work » Fixed

@thank you all , patch at #4 is has been pushed to 8.x-1.x branch.

hardik_patel_12’s picture

@kishor_kolekar , thanks for your patch but i think patch at #4 is already done same thing.

kishor_kolekar’s picture

sorry I missed it @Hardik_Patel_12

Status: Fixed » Closed (fixed)

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

kristen pol’s picture

Issue tags: -Drupal 9 readiness

Removing outdated tag.