jaydee1818 → created an issue.
jaydee1818 → created an issue.
Yes, I got that issue too actually. This re-roll handles that.
I've created a new patch to deal with Drupal 11 issues. Seems to work.
Current patch is failing. Here's a new one.
I also experienced this issue. #3 works as designed.
jaydee1818 → created an issue.
It's not possible to follow along with this guide using the latest version of Drupal (10.3) using the Rules module:
% ddev composer req drupal/rules
In PackageDiscoveryTrait.php line 332:
Could not find a version of package drupal/rules matching your minimum-stab
ility (stable). Require it with an explicit version constraint allowing its
desired stability.
require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-m|--minimal-changes] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [<packages>...]
Composer [req drupal/rules] failed, composer command failed: exit status 1. stderr=
jon@MacBook-Pro-4 drupal-test % ddev composer require 'drupal/rules:^3.0@alpha'
./composer.json has been updated
Running composer update drupal/rules
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/rules 3.0.0-alpha1 requires drupal/core ~8.0 -> found drupal/core[8.0.0, ..., 8.9.20] but the package is fixed to 10.3.0 (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.
- drupal/rules[3.0.0-alpha2, ..., 3.0.0-alpha5] require drupal/typed_data * -> found drupal/typed_data[dev-1.x, dev-2.0.x, dev-2.1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.x-dev (alias of dev-2.0.x), 2.1.x-dev (alias of dev-2.1.x)] but it does not match your minimum-stability.
- drupal/rules 3.0.0-alpha6 requires drupal/typed_data 1.x-dev -> found drupal/typed_data[dev-1.x, 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
- drupal/rules 3.0.0-alpha7 requires drupal/core ^8.8.2 || ^9 -> found drupal/core[8.8.2, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.3.0 (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.
- drupal/rules 3.0.0-alpha8 requires drupal/typed_data ^1.0 -> found drupal/typed_data[dev-1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
- Root composer.json requires drupal/rules ^3.0@alpha -> satisfiable by drupal/rules[3.0.0-alpha1, ..., 3.0.0-alpha8].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Composer [require drupal/rules:^3.0@alpha] failed, composer command failed: exit status 2. stderr=
% ddev composer require 'drupal/rules:^3.0@alpha' -W
./composer.json has been updated
Running composer update drupal/rules --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/rules 3.0.0-alpha1 requires drupal/core ~8.0 -> found drupal/core[8.0.0, ..., 8.9.20] but these were not loaded, likely because it conflicts with another require.
- drupal/rules[3.0.0-alpha2, ..., 3.0.0-alpha5] require drupal/typed_data * -> found drupal/typed_data[dev-1.x, dev-2.0.x, dev-2.1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 2.0.x-dev (alias of dev-2.0.x), 2.1.x-dev (alias of dev-2.1.x)] but it does not match your minimum-stability.
- drupal/rules 3.0.0-alpha6 requires drupal/typed_data 1.x-dev -> found drupal/typed_data[dev-1.x, 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
- drupal/rules 3.0.0-alpha7 requires drupal/core ^8.8.2 || ^9 -> found drupal/core[8.8.2, ..., 8.9.20, 9.0.0, ..., 9.5.11] but these were not loaded, likely because it conflicts with another require.
- drupal/rules 3.0.0-alpha8 requires drupal/typed_data ^1.0 -> found drupal/typed_data[dev-1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
- Root composer.json requires drupal/rules ^3.0@alpha -> satisfiable by drupal/rules[3.0.0-alpha1, ..., 3.0.0-alpha8].
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Composer [require drupal/rules:^3.0@alpha -W] failed, composer command failed: exit status 2. stderr=
jaydee1818 → created an issue.
jaydee1818 → created an issue.
Ok then - how about this idea. Add the option to override the current template? Set to false by default but change it to true if that behaviour suits your use-case?
{
"title": "Banner Variant One",
"icon": "<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M8 16h8v2H8zm0-4h8v2H8zm6-10H6c-1.1 0-2 .9-2 2v16c0 1.1.89 2 1.99 2H18c1.1 0 2-.9 2-2V8l-6-6zm4 18H6V4h7v5h5v11z\"/></svg>",
"description": "2-col - LHS: Text, RHS: Image",
"override": true,
"html": "<div>My template</div>"
},
jaydee1818 → created an issue.
jaydee1818 → created an issue.
jaydee1818 → created an issue.
jaydee1818 → created an issue.
The entire module is only compatible with CKE 4 as far as I know.
I'm also experiencing this
Fix a bug that preventing patch being applied.
This patch is based on #4 ... when I tried that one, my "Read more" link printed out multiple times. I've refactored the JS so that it makes use of the drupal/once library. It now works as expected. Please review.
Tests are failing here due to issue here: https://www.drupal.org/project/examples/issues/3376999 🐛 Field Example Add Field text outdated in Functional tests in D10.1 Needs review
Increase version to check to 10.1.0
Adds a service to check the current version before running tests pre 10.0.0
Try again.
This one should be backwards compatible.
Fixed here: https://www.drupal.org/project/examples/issues/3376999 🐛 Field Example Add Field text outdated in Functional tests in D10.1 Needs review
This patch fixes the issue here and for the Config Entity Example module.
jaydee1818 → created an issue.
This patch updates the clickLink text in the createField method of theFieldExampleBrowserTestBase class.
jaydee1818 → created an issue.
This patch actually removes the jQuery lib from the .libraries file. Disregard first patch.
I've re-written the JS for this module to modernise and improve it. The main changes are:
- Use modern Vanilla JS and remove jQuery
- Use the once library to prevent multiple loads
- Add accordion code to Drupal.behaviors
Below, there is a sub-heading titled "Order of import" which contradicts this point.
After applying patch #53, everything seems to work well, but when I click on a group to expand it, I see the element is focused with a green border as per usual, but I'm also seeing a duplicate red asterisk printing on top of the border. Is this by design or is it a bug?
jaydee1818 → created an issue.
Take two - here's a patch that does the trick.
Here's a patch that does the trick.
jaydee1818 → created an issue.
MR works for me. Cheers.
jaydee1818 → created an issue.
I can also confirm that the patch at #2 squashes the error message.
I experienced this issue today.
I'm using Drupal v9.5.3 running on PHP 8.1. I am also using the latest version of the Conditional Fields module (v4.0.0-alpha2).
To replicate, install the module, go to a content type and click on the `Manage Dependencies` tab. For me, I added a dependency on one filled to be visible when another field is `filled`. Then click "Add dependency". Like so:
On the confirmation page, simply click `Save settings` to see the error:
jaydee1818 → created an issue.
#7 works for me too.
jaydee1818 → created an issue.
I'm running into this as well on my Apple M1. When spinning up conatainers using a DDev setup, I get:
Status: Downloaded newer image for drupalci/chromedriver:production
docker.io/drupalci/chromedriver:production
Network ddev-site-name_default Created
chromedriver The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested