Drupal 11 compatibility fixes for conditional_fields

Created on 4 October 2024, 2 months ago

Problem/Motivation

We are using the conditional_fields module on several of our websites that we want to migrate to Drupal 11.

Proposed resolution

  • Implement a Drupal 11 compatible version of this module.

Remaining tasks

Publish, review and validate MR.

Feature request
Status

Active

Version

4.0

Component

Code

Created by

🇫🇷France mably

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

Merge Requests

Comments & Activities

  • Issue created by @mably
  • Pipeline finished with Failed
    2 months ago
    Total: 1130s
    #301275
  • Pipeline finished with Failed
    2 months ago
    Total: 475s
    #301284
  • Pipeline finished with Failed
    2 months ago
    #301289
  • Pipeline finished with Canceled
    2 months ago
    Total: 132s
    #301296
  • Pipeline finished with Canceled
    2 months ago
    Total: 67s
    #301297
  • Pipeline finished with Failed
    2 months ago
    Total: 1089s
    #301298
  • Pipeline finished with Canceled
    about 2 months ago
    Total: 93s
    #301523
  • Pipeline finished with Running
    about 2 months ago
    #301528
  • Pipeline finished with Canceled
    about 2 months ago
    #301526
  • Pipeline finished with Failed
    about 2 months ago
    Total: 487s
    #301548
  • Pipeline finished with Failed
    about 2 months ago
    Total: 1008s
    #301551
  • Pipeline finished with Failed
    about 2 months ago
    Total: 1462s
    #301559
  • Pipeline finished with Canceled
    about 2 months ago
    Total: 901s
    #301604
  • Pipeline finished with Success
    about 2 months ago
    Total: 1166s
    #301658
  • 🇫🇷France mably

    All tests are green 🎉

  • Pipeline finished with Success
    about 2 months ago
    Total: 989s
    #301677
  • Pipeline finished with Running
    about 2 months ago
    Total: 4489s
    #301613
  • Hello,

    I have created a patch for 4.0.0-alpha5.

  • 🇭🇺Hungary nagy.balint

    Any news on this issue?

    What do we need to commit this?

  • Pipeline finished with Failed
    27 days ago
    Total: 273s
    #331978
  • Pipeline finished with Failed
    27 days ago
    Total: 825s
    #331979
  • Pipeline finished with Canceled
    27 days ago
    Total: 92s
    #331994
  • Pipeline finished with Failed
    27 days ago
    Total: 522s
    #331996
  • Pipeline finished with Canceled
    27 days ago
    Total: 479s
    #332002
  • Pipeline finished with Success
    27 days ago
    Total: 1772s
    #332013
  • 🇮🇳India rahul1707

    Tested MR !58 changes in Drupal 10.3 and Drupal 11, functionality is working fine and also upgrade status is showing no problem found.

    Changing status to RTBC.

  • 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    Why do we have a duplicate issue created a month ago while there was already one existing with contribution of original maintainers of this project? (not talking about me here)

    Thanks for all the efforts and any contribution is very much appreciated to move on. But please let us keep things sorted and do not let us outframe efforts in other issues already made and please MR this here if required into the former compatibility issue exisiting already since March of this year.

    Million thanks! And sorry for any inconveniened feelings about it. But it would not be very nice regarding the previous issue work done. This is why we usually follow the rule to mark the newer as duplicate of the former. This way we do not loose track of overlapping fixes and do not loose track of credits on efforts in the issues.

  • 🇫🇷France mably

    Ok for me, as long as we get a Drupal 11 release quick.

    That was a lot of hard work though.

  • 🇫🇷France mably

    Code pushed to original issue 📌 Automated Drupal 11 compatibility fixes for conditional_fields Needs review .

  • 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    That was a lot of hard work though.

    Indeed! Very impressive and very much appreciated. It was hard for me to make this very unsatisfying step. But it is a common procedure on Drupal to prevent credit and fix overlapping issues. And I am sorry for the frustration. I recommend to use the issue search before starting an new issue. Or if you feel the original issue is not going in the right direction or too slow, to ping contributors or to discuss in the issue how to move on. I think your contributions are awesome and can move things forward a lot. +1 And your thoughts will weight. So I don't want to demoitilize you in any way and hope you keep up your awesome work! Thanks for pushing into the previous issue!

  • 🇫🇷France mably

    You're welcome :)

    I guess that's the "Automated" part of the other issue that got me wrong.

Production build 0.71.5 2024