Account created on 5 March 2008, almost 17 years ago
#

Recent comments

🇬🇧United Kingdom ChandeepKhosa

I have confirmed Gabriela's account as she posted this issue https://www.drupal.org/project/role_paywall/issues/3412356 💬 feature to select the paywall block to use as barrier no longer exists. Active

🇬🇧United Kingdom ChandeepKhosa

Hi Daniel,

There are now 3 dunning levels before cancellation in the latest version of this module. I hope that helps.

🇬🇧United Kingdom ChandeepKhosa

I'm not sure if this will resolve your exact issue, but I had problems getting recurring payments working until an issue was fixed in commerce_stripe, using 1.0.0-rc10 of that makes it work (1.0.0 didn't)

🇬🇧United Kingdom ChandeepKhosa

For anyone else this might help, I had the following errors with commerce_stripe 1.0, with Live payment gateway, but payment gets taken smoothly when downgrading to 1.0-rc10

Payment used to fail before using the patch here https://www.drupal.org/project/commerce_stripe/issues/3171408 Allow off_session payment intents for recurring payments Fixed

I'm currently not using any commerce core or contrib module patches. I'm also using commerce_recurring 1.0-rc1

Perhaps this issue should be re-opened until it's working in the latest release?

🇬🇧United Kingdom ChandeepKhosa

I can also confirm that the patches continue to apply smoothly for 1.0-rc10 & 1.0. It would be really great if we could look at getting this merging in soon :)

🇬🇧United Kingdom ChandeepKhosa

Unless I've misunderstood this issue, I believe that this may no longer need a fix as menu_link_weight is working perfectly for me.
I am using Drupal core (9.5.9), menu_link_weight (1.0.0-beta5) & menu_admin_per_menu (1.5.0).

🇬🇧United Kingdom ChandeepKhosa

This is a duplicate of the issue I've just linked, which is now working for me :)

🇬🇧United Kingdom ChandeepKhosa

This is now working for me in Drupal 9 (hopefully you've upgraded from Drupal 8), I've added details here, take a look and see if it also works for you :)
https://www.drupal.org/project/conditional_fields/issues/2902164#comment... 🐛 Controlled-by fields inside a Paragraph don't work Needs work

🇬🇧United Kingdom ChandeepKhosa

If your site is now using Drupal 9, try this and hopefully it will also work for you :) https://www.drupal.org/project/conditional_fields/issues/2902164#comment... 🐛 Controlled-by fields inside a Paragraph don't work Needs work

🇬🇧United Kingdom ChandeepKhosa

This is now working with Drupal 9 for me, just tested it, feel free to take a look and see if it also works for you :)
FYI the 'Manage dependencies' tab doesn't show on paragraphs yet, but if you follow my instructions it will hopefully work smoothly for you too.
https://www.drupal.org/project/conditional_fields/issues/2902164#comment... 🐛 Controlled-by fields inside a Paragraph don't work Needs work

🇬🇧United Kingdom ChandeepKhosa

I tested the patch in #106 successfully, just like the tester in #108. I am using Drupal core 9.5.3, paragraphs 8.x-1.15 & entity_reference_revisions 8.x-1.10.

If there is anyone who can't get the patch to apply, please check you're not using 4.0.0-alpha1 of this module, you will first need to switch to the dev version, using `composer require 'drupal/conditional_fields:4.x-dev@dev'`.

I tested by creating a paragraph type and adding a List (text) field to it with 2 values. I then went to /admin/structure/conditional_fields/paragraph, selected the paragraph type and added dependencies to selectively show fields that were hidden depending on the value of the List (text) field.

Then finally, I added a paragraph field to a content type, and saw that the fields stopped being hidden and displayed based on my input for the List (text) field. I tested this successfully with the radio button & select form displays.

Thanks everyone for your assistance in getting this working.

For extra clarity on how I got this working, and because it can get a little tricky to use it for the first time, or after not using the interface for a while, I have also added screenshots.

As this is now working for a few of us, tests are passing and to make things easier for a wider set of new people stumbling across this issue, I would like to recommend that we get this committed and closed, then open new issues for more advanced/complex use cases to build on top of this great foundation. I hope that will be fine with everyone :)

🇬🇧United Kingdom ChandeepKhosa

I also experienced this issue on a site running Drupal 9.5.1 when running `composer require drupal/lb_ux`

Using version ^1.0@beta for drupal/lb_ux
./composer.json has been updated
Running composer update drupal/lb_ux
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Info from https://repo.packagist.org: #StandWithUkraine
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/lb_ux ^1.0@beta -> satisfiable by drupal/lb_ux[1.0.0-beta1, 1.0.0-beta2].
    - drupal/lb_ux[1.0.0-beta1, ..., 1.0.0-beta2] require drupal/core ^8 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but the package is fixed to 9.5.1 (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.

My workaround was to run composer require 'drupal/lb_ux:^1.0@beta' listed on the latest release page https://www.drupal.org/project/lb_ux/releases/8.x-1.0-beta2

Production build 0.71.5 2024