Automated Drupal 10 compatibility fixes with composer file

Created on 7 December 2023, 12 months ago
Updated 18 January 2024, 10 months ago

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Fixed

Version

2.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • 🇹🇭Thailand Nick Hope

    I'm preparing a site for upgrading from D9.5.11 to D10.2.

    In D.5.11, $plugins['entity:taxonomy_term']['class'] = 'Drupal\taxonomy\Plugin\views\argument_validator\TermName'; in media_taxonomy_filter.views.inc gives me Page Not Found, with no error messages, on pages using this module.

    Pages are found successfully when $plugins['entity:taxonomy_term']['class'] = 'Drupal\views\Plugin\views\argument_validator\Entity'; is used instead, as in the other D10-compatibility MR at https://www.drupal.org/project/media_taxonomy_filter/issues/3288527#comm... 📌 Automated Drupal 10 compatibility fixes Needs review . But there's no composer.json with that MR. so installing it with Composer gives No valid composer.json was found... errors.

    I don't have the experience to know which of ...\argument_validator\TermName or ...\argument_validator\Entity is correct or preferable in this case.

  • Status changed to Fixed 11 months ago
  • I made a new drupal 10 release, thank you for your help.

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

Production build 0.71.5 2024