Add core_version_requirement: ^8 || ^9 to views_fieldsets.info.yml to designate that the module is compatible with Drupal 9. See https://www.drupal.org/node/3070687.

CommentFileSizeAuthor
#2 3126203-2.patch288 bytesmo_farhaz
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mo_farhaz created an issue. See original summary.

mo_farhaz’s picture

Assigned: mo_farhaz » Unassigned
Status: Active » Needs review
FileSize
288 bytes

core version requirement added.
please review it

KapilV’s picture

Issue tags: +Drupal 9 compatibility

  • pifagor committed eea8080 on 8.x-3.x
    Issue #3126203 by mo_farhaz: Drupal 9 readiness
    
pifagor’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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

NickoLaz’s picture

I have apply a patch in composer.json

        "enable-patching": true,
        "patches": {
            "drupal/views_fieldsets": {
                "Drupal 9 support": "https://www.drupal.org/files/issues/2020-04-09/3126203-2.patch"
            }
        }

but when run composer require drupal/views_fieldsets there is still conflict dependency problem

Problem 1
    - Root composer.json requires drupal/views_fieldsets ^3.3 -> satisfiable by drupal/views_fieldsets[3.3.0].
    - drupal/views_fieldsets 3.3.0 requires drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.13] but the package is fixed to 9.1.6 (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.
nojj’s picture

i have the same problem. Any solution?

madeingnecca’s picture

Me too. Dev version is working fine with D9, but it would be great if we could have a stable release (I am not comfortable with the idea of having a dev version in my production websites). I don't understand if there is something serious blocking or if the maintainer just needs to create the D9 release.