Any chance of Drupal 11 compliant release for this?

Thanks

CommentFileSizeAuthor
#6 3498382-d11.patch1.2 KBtunic

Issue fork field_group_label-3498382

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

sirclickalot created an issue. See original summary.

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented

Hi, let me try to do the upgrade.

tunic changed the visibility of the branch 3498382-drupal-11-release to hidden.

tunic changed the visibility of the branch 3498382- to hidden.

tunic opened merge request !6

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented
StatusFileSize
new 3498382-d11.patch1.2 KB

Added patch for testing.

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented
Title: Drupal 11 release for this? » Drupal 11 release
Category: Support request » Feature request

tunic credited alemadlei.

tunic credited brightbold.

tunic credited timohuisman.

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented
sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset, UK
commented

@tunic,

I have patched my local version and flushed all caches and done a database updated just in case.

All working as before :-)

However, when I go to (dry run) and re-try an update to the Field Group module itself using...

composer require 'drupal/field_group:^4.0'  --with-all-dependencies --dry-run

I am still seeing the 'Problems' ...

Problem 1
    - Root composer.json requires drupal/field_group ^4.0, found drupal/field_group[dev-4.x, 4.0.0-alpha1, 4.0.0, 4.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - drupal/field_group_label is locked to version 2.0.0 and an update of this package was not requested.
    - drupal/field_group_label 2.0.0 requires drupal/field_group ^3.4 -> found drupal/field_group[dev-3.x, 3.4.0, 3.5.0, 3.6.0, 3.x-dev (alias of dev-3.x)] but it conflicts with your root composer.json require (^4.0).
  Problem 3
    - drupal/popup_field_group is locked to version 1.9.0 and an update of this package was not requested.
    - drupal/popup_field_group 1.9.0 requires drupal/field_group * -> found drupal/field_group[dev-1.x, dev-3.x, dev-4.x, 1.0.0-rc3, ..., 1.x-dev (alias of dev-1.x), 3.0.0-beta1, ..., 3.x-dev (alias of dev-3.x), 4.0.0-alpha1, 4.0.0, 4.x-dev] but these were not loaded, likely because it conflicts with another require.

Another community member has assured me that the Field Group Popup module (Problem 3 ) is a red-herring here.

What am I missing?

Thanks

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented

I guess I forgot to add compatibility with Field Group 4.x.

Can you try the updated issue fork?

  • tunic committed d75c5b97 on 2.x 
    Issue #3498382: Drupal 11 support
tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented

Let's be optimistic and merge this.

crzdev’s picture

crzdev commented

Integrated changes seems quite logical, thanks @sanzante!

crzdev’s picture

crzdev commented

New beta release created for testing purposes, that one will replace current stable when this issue is fixed!

crzdev’s picture

crzdev commented
Status: Active » Needs review
crzdev’s picture

crzdev commented
Title: Drupal 11 release » Drupal 11 release compatible with field group 4
sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset, UK
commented

Thank you for all the efforts over the last 24 hour folks.

I can can confirm that 2.1.0.-beta-1 all works as expected and UNblocks the Field Group update to 4.x

tunic’s picture

tunic
he/him
Primary language Spanish
Location Madrid
commented
Status: Needs review » Fixed

2.1.0-beta1 has been promoted to 2.1.0.

Closing as bot is now focused on D12 compatibility.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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