🇺🇸United States @tjtj

tjtj → created an issue.

tjtj → created an issue.

tjtj → created an issue.

tjtj → created an issue.

asset-package.org says

 @kurkle/color npm-asset/kurkle--color

css color parsing, manupulation and conversion

Latest Release: 0.4.0 at May 29, 2025, 6:41:46 AM (6 months ago)

Keywords: color colour css hsl hex rgb rgba hwb hsv cmyk

 Homepage

 Repository

 License: MIT

 chartjs-plugin-autocolors-typescript npm-asset/chartjs-plugin-autocolors-typescript

A fork of kurkle/chartjs-plugin-autocolors (Automatic color generation for Chart.js) with types

Latest Release: 0.2.5 at Apr 18, 2023, 12:51:37 PM (2 years ago)

Keywords: chart.js plugin color palette generator auto

But 0.3.4 is in fact there at https://registry.npmjs.org/@kurkle/color/-/color-0.3.4.tgz

Gemini says:

Verifying Asset Packagist

I've confirmed that version 0.3.4 of @kurkle/color is indeed absent from Asset Packagist. However, the tarball is readily available on the npm registry, solidifying the initial assessment: Asset Packagist is out of sync with npm for this particular package version. This confirms the initial diagnosis.

Verifying Asset Packagist

I've confirmed that version 0.3.4 of @kurkle/color is indeed absent from Asset Packagist. However, the tarball is readily available on the npm registry, solidifying the initial assessment: Asset Packagist is out of sync with npm for this particular package version. This confirms the initial diagnosis.

Considering Workarounds & Retry

Given the confirmed absence of 0.3.4, I've shifted focus. I now need to investigate forcing an Asset Packagist update, or determining if a scoped package issue exists. I'm also considering potential workarounds to bypass the broken version, or adjusting dependency constraints to get the Drupal site install back on track.

Devising Potential Resolutions

I'm now contemplating several potential solutions. First, if version 0.3.2 or 0.3.3 of @kurkle/color are accessible on Asset Packagist, I'll explore downgrading or upgrading to those as a workaround, but I must take chart.js's dependency constraints into account. Alternatively, I'm considering using oomphinc/composer-installers-extender to pull directly from npm, or employing the "VCS" workaround by defining a package repository pointing to the git repo. Removing the root constraint is also a viable initial step to allow for any compatible version to be installed.

Resolving Version Conflict

I've discovered that version 0.5.1 integrates with other versions of @kurkle/color that are present on Asset Packagist. My immediate plan involves verifying the current state of @kurkle/color on Asset Packagist and suggesting the removal of the specific 0.3.4 root dependency lock. The goal is to allow Composer to select a suitable version that's already available, like 0.3.2 or 0.3.3. Considering chart.js's broad version constraint, this is the most direct solution. I'll test to see if 0.3.4 is strictly required.

Identifying the Problem

I've confirmed a specific problem with @kurkle/color version 0.3.4. It exists on NPM but isn't reflected in Asset Packagist's metadata, a known sync issue for scoped packages.

Addressing the Dependency Issue

I've determined that the conflict stems from a strict dependency in the user's composer.json file. Specifically, npm-asset/kurkle--color is pinned to version 0.3.4, which isn't available through Asset Packagist. The primary solution is to relax this constraint, letting Composer resolve a compatible version. If that fails, I've outlined a less elegant workaround using a direct NPM repository declaration. I will first explain the root cause and then offer these two solutions.

This confirms the diagnosis: Asset Packagist is out of sync with the official NPM registry for this specific version. While NPM has version 0.3.4, Asset Packagist hasn't indexed it yet, so it tells Composer "this version doesn't exist."

Since your composer.json forces an exact match (== 0.3.4.0), the update fails.

Here is the fix. We will remove the strict requirement from your root file and let chart.js pick a version that is available (like 0.3.2 or 0.3.3), which satisfies its requirement of >=0.3.0,<0.4.0.

Fix: Allow Composer to Pick a Working Version

Run these commands in your terminal:

1. Remove the strict lock from your root configuration:

   Bash

   composer remove npm-asset/kurkle--color --no-update
   

2. Update chart.js and its dependencies:

   Bash

   composer update npm-asset/chart.js --with-all-dependencies
   

Why this works: chart.js does not strictly require version 0.3.4; it just needs anything between 0.3.0 and 0.4.0. By removing your manual lock, Composer will automatically fall back to the latest version Asset Packagist actually has (likely 0.3.2 or 0.3.3), resolving the error immediately.

Alternative: If You MUST Have Version 0.3.4

If you absolutely need version 0.3.4 (unlikely for standard Drupal usage), you must manually tell Composer where to find that specific file since Asset Packagist won't.

Add this to your composer.json under the "repositories" section:

JSON

{
    "type": "package",
    "package": {
        "name": "npm-asset/kurkle--color",
        "version": "0.3.4",
        "type": "npm-asset",
        "dist": {
            "url": "https://registry.npmjs.org/@kurkle/color/-/color-0.3.4.tgz",
            "type": "tar"
        }
    }
}

Thjis fixes it. But the problem is the npm repository.

Supposedly JQuery UI is in core, but I have all the above dependencies. How does one uninstall it without munging my site?

tjtj → created an issue.

tjtj → created an issue.

Please release a new patchyed version

2.1.0 also says it is incompatible.
Package operations: 0 installs, 1 update, 0 removals
- Downloading drupal/views_base_url (2.1.0)
- Downgrading drupal/views_base_url (3.0.0-alpha1 => 2.1.0): Extracting archive
[warning] (Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 11.2.4:
* Views Base URL

I see this too and am confused about what to do.

I see this too and am confused about what to do.

I installed 3.0.0-alpha1, but get
(Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 11.2.4:
* Views Base URL

I get this and also webform_location_places. How do I fix it?

This is a fundamental problem with Drupal. Critical modules (that cannot be removed without munging a site) do not get updated in a timely manner and thus make upgrades to new releases very difficult. Someone at Drupal needs to investigate whether maintainers are still alive!

So, release this already!

Updating cookies to version 2.0 fixed this

tjtj → created an issue.

This makes it hard to maintain the site using Composer. php errors are critical.

hmmm. I removed the cleantalk directory and unzipped the above zip file to replace it. but I still get:
1157484 23/Apr 14:46 php Error Error: Class
"Drupal\cleantalk\EventSubscriber\BootSubscriber" not
found in
Drupal\Component\DependencyInjection\Container->create
Service() (line 259 of
/home/jamesrom/public_html/blogs/we

Can you release a new version I can install with Composer? I just6 got an email that updates are ready to be used. Is that fir this new version?

Reverting to 9.5 stopped the error

tjtj → created an issue.

tjtj → created an issue.

Please release this!

What is holding up the release?

I went through the steps in README.md, in /public_html/blogs/web/modules/contrib/charts/modules/charts_chartjs, but I do not get a charts library. The last step gives:

-bash: npm-asset/chartjs-adapter-date-fns:^3.0: No such file or directory
-bash: npm-asset/chartjs-plugin-datalabels:^2.0: No such file or directory

I tried both ways in composer.json.

"extra": {
    "installer-types": ["npm-asset"],
    "installer-paths": {
        "web/libraries/chart.js": ["npm-asset/chart.js"],
        "web/libraries/chartjs-adapter-date-fns": [
          "npm-asset/chartjs-adapter-date-fns"
        ],
        "web/libraries/chartjs-plugin-datalabels": [
          "npm-asset/chartjs-plugin-datalabels"
        ],
    },
}

NOTE: If this isn't working, try instead adding:
"extra": {
    "installer-types": ["npm-asset"],
    "installer-paths": {
        ...
        "web/libraries/{$name}": ["type:drupal-library", "vendor:npm-asset"]
    },
}

I reinstalled charts, and CDN was selected. And the error is gone. Sorry about bothering you.

That is really complicated. Shouldn't charts install the necessary library for me?

where do I get charts_chartjs?

Please provide some info on how to install the chart.js library too.

11.1.4.
I get a message in reports that I need a plugin.

Chart.js Library
Not Installed
You are missing the Chart.js library in your Drupal installation directory and you have opted not to use a CDN. Please either enable use of the CDN in the Chart Settings under the Advanced tab or see the README file inside charts_chartjs for instructions to install the library.

So I went the Charts setting to fix this, and pow!

tjtj → created an issue.

Release this already! Its 3 months!!

That is beautiful. Thanks!

Ah. I uninstalled it, reinstalled it, and node_counter is there

node_counter is NOT in my database. How do I create it? Surely installing statistics should create it?

tjtj → created an issue.

What about using jquery.cycle2?

Does the released D11 views_slideshow require this? My slideshow no longer slides in D11.

tjtj → created an issue.

tjtj → created an issue.

Please release this

So please release D11 version

Please release the D11 version!

So release a D11 version already

So please release the D11 version. I do not understand why it takes so long. Or at least release a patch.

tjtj → created an issue.

I was unable to get the patch to work in composer.json

    "extra": {
       "patches": {
           "drupal/zurb_foundation": {
               "temporary patch": "https://git.drupalcode.org/project/zurb-foundation/-/merge_requests/30.patch"
           }
       },

so I unstalled ZF and was able to update to 11.1.2.
Then I reinstalled the theme manually (from the tar file) and applied your patch.

But now, the slideshow displays all the images at once. Any suggestions?
Thanks, Jim

I had to uninstall Zurb Foundation. I should not have had to. Then

composer update -W 

worked and a new lock file was created. Why didn't my composer patch work?

# composer update
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/core-recommended ^11 -> satisfiable by drupal/core-recommended[11.0.0-alpha1, ..., 11.x-dev].
    - Root composer.json requires drupal/zurb_foundation ^9.0@beta -> satisfiable by drupal/zurb_foundation[9.0.0-beta1].
    - drupal/core-recommended 11.0.0-rc1 requires drupal/core 11.0.0-rc1 -> satisfiable by drupal/core[11.0.0-rc1].
    - drupal/core-recommended 11.0.0-alpha1 requires drupal/core 11.0.0-alpha1 -> satisfiable by drupal/core[11.0.0-alpha1].
    - drupal/core-recommended 11.0.0-beta1 requires drupal/core 11.0.0-beta1 -> satisfiable by drupal/core[11.0.0-beta1].
    - drupal/core-recommended 11.0.0 requires drupal/core 11.0.0 -> satisfiable by drupal/core[11.0.0].
    - drupal/core-recommended 11.0.1 requires drupal/core 11.0.1 -> satisfiable by drupal/core[11.0.1].
    - drupal/core-recommended 11.0.10 requires drupal/core 11.0.10 -> satisfiable by drupal/core[11.0.10].
    - drupal/core-recommended 11.0.11 requires drupal/core 11.0.11 -> satisfiable by drupal/core[11.0.11].
    - drupal/core-recommended 11.0.2 requires drupal/core 11.0.2 -> satisfiable by drupal/core[11.0.2].
    - drupal/core-recommended 11.0.3 requires drupal/core 11.0.3 -> satisfiable by drupal/core[11.0.3].
    - drupal/core-recommended 11.0.4 requires drupal/core 11.0.4 -> satisfiable by drupal/core[11.0.4].
    - drupal/core-recommended 11.0.5 requires drupal/core 11.0.5 -> satisfiable by drupal/core[11.0.5].
    - drupal/core-recommended 11.0.6 requires drupal/core 11.0.6 -> satisfiable by drupal/core[11.0.6].
    - drupal/core-recommended 11.0.7 requires drupal/core 11.0.7 -> satisfiable by drupal/core[11.0.7].
    - drupal/core-recommended 11.0.8 requires drupal/core 11.0.8 -> satisfiable by drupal/core[11.0.8].
    - drupal/core-recommended 11.0.9 requires drupal/core 11.0.9 -> satisfiable by drupal/core[11.0.9].
    - drupal/core-recommended 11.0.x-dev requires drupal/core 11.0.x-dev -> satisfiable by drupal/core[11.0.x-dev].
    - drupal/core-recommended 11.1.0-rc1 requires drupal/core 11.1.0-rc1 -> satisfiable by drupal/core[11.1.0-rc1].
    - drupal/core-recommended 11.1.0-beta1 requires drupal/core 11.1.0-beta1 -> satisfiable by drupal/core[11.1.0-beta1].
    - drupal/core-recommended 11.1.0 requires drupal/core 11.1.0 -> satisfiable by drupal/core[11.1.0].
    - drupal/core-recommended 11.1.1 requires drupal/core 11.1.1 -> satisfiable by drupal/core[11.1.1].
    - drupal/core-recommended 11.1.2 requires drupal/core 11.1.2 -> satisfiable by drupal/core[11.1.2].
    - drupal/core-recommended 11.1.x-dev requires drupal/core 11.1.x-dev -> satisfiable by drupal/core[11.1.x-dev].
    - drupal/core-recommended 11.x-dev requires drupal/core 11.x-dev -> satisfiable by drupal/core[11.x-dev].
    - drupal/zurb_foundation 9.0.0-beta1 requires drupal/core ^9.3 || ^10 -> satisfiable by drupal/core[9.3.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev].
    - Conclusion: don't install drupal/core 11.1.x-dev (conflict analysis result)
    - Conclusion: don't install drupal/core 11.x-dev (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0-alpha1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0-beta1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0-rc1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.0 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.2 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.3 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.4 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.5 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.6 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.7 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.8 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.9 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.10 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.0.11 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0-beta1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0-rc1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.0 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.1 (conflict analysis result)
    - Conclusion: don't install drupal/core 11.1.2 (conflict analysis result)
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[8.7.0-alpha1, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].

zurb foundation has a patch in composer.json:

    "extra": {
        "patches": {
            "drupal/zurb_foundation": {
                "temporary patch": "https://git.drupalcode.org/project/zurb-foundation/-/merge_requests/30.p..."
            }
        },
 

Composer.json says ^11. But how do I fix the core 10.4.2

# composer prohibits drupal/core 11.1
drupal/core-recommended    10.4.2 requires         drupal/core (10.4.2)
drupal/core                11.1.0 requires         symfony/console (^7.2)
drupal/recommended-project -      does not require symfony/console (but v6.4.17 is installed)
drupal/core                11.1.0 requires         symfony/dependency-injection (^7.2)
drupal/recommended-project -      does not require symfony/dependency-injection (but v6.4.16 is installed)
drupal/core                11.1.0 requires         symfony/event-dispatcher (^7.2)
drupal/recommended-project -      does not require symfony/event-dispatcher (but v6.4.13 is installed)
drupal/core                11.1.0 requires         symfony/filesystem (^7.2)
drupal/recommended-project -      does not require symfony/filesystem (but v6.4.13 is installed)
drupal/core                11.1.0 requires         symfony/finder (^7.2)
drupal/recommended-project -      does not require symfony/finder (but v6.4.17 is installed)
drupal/core                11.1.0 requires         symfony/http-foundation (^7.2)
drupal/recommended-project -      does not require symfony/http-foundation (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/http-kernel (^7.2)
drupal/recommended-project -      does not require symfony/http-kernel (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/mailer (^7.2)
drupal/recommended-project -      does not require symfony/mailer (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/mime (^7.2)
drupal/recommended-project -      does not require symfony/mime (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/routing (^7.2)
drupal/recommended-project -      does not require symfony/routing (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/serializer (^7.2)
drupal/recommended-project -      does not require symfony/serializer (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/validator (^7.2)
drupal/recommended-project -      does not require symfony/validator (but v6.4.18 is installed)
drupal/core                11.1.0 requires         symfony/process (^7.2)
drupal/recommended-project -      does not require symfony/process (but v6.4.15 is installed)
drupal/core                11.1.0 requires         symfony/yaml (^7.2)
drupal/recommended-project -      does not require symfony/yaml (but v6.4.18 is installed)
drupal/core                11.1.0 requires         doctrine/annotations (^2.0)
drupal/recommended-project -      does not require doctrine/annotations (but 1.14.4 is installed)
drupal/core                11.1.0 requires         symfony/psr-http-message-bridge (^7.2)
drupal/recommended-project -      does not require symfony/psr-http-message-bridge (but v6.4.13 is in

Why can't you just release this? Patching requires munging with composer.json.

https://blogs.jamesrome.net/drupal10_upgrade

But I was referring to Drupal-CMS.

Webform has now been updated, and users of your theme cannot update to Drupal 11! Please update it.

tjtj → created an issue.

webform 6.3.0-alpha1 is released. Please release this.

where is the link to 6.3 alpha?

I can live with an unstable webforms, since it will be updated by composer when it is totally fixed. But I cannot do the move to D11 on a test site until you release a dev version of this module.

There is no version number in jquery_ui.menu.info.yml

"name: jQuery UI Menu
type: module
description: 'Provides jQuery UI Menu library.'
package: jQuery UI
core_version_requirement: ^9.2 || ^10 || ^11
dependencies:
  - jquery_ui:jquery_ui (>=8.x-1.7)ent: ^9.2 || ^10 || ^11

But my versions that work have this in them:

# Information added by Drupal.org packaging script on 2024-05-30
version: '2.1.0'
project: 'jquery_ui_menu'
datestamp: 1717031362

I added this, and it fixed it!

But why wasn't it added by the packaging system?

https://www.drupal.org/project/webform/releases/6.3.x-dev →

How do I get a patch to apply or a new D11 release? This is stop[ping my D11 upgrade. Webform has 6.3 out.

Extend does not show the version of these modules either. For example, JQuery UI:

Machine name: jquery_ui_datepicker

Requires:

• jQuery UI (>=8.x-1.7) (incompatible with version * ? *)

Required by:

• Webform jQueryUI Datepicker

Module path: modules/contrib/jquery_ui_datepicker

tjtj → created an issue.

so how do I install the working D11 version?

tjtj → created an issue.

Thanks. Why not put a link to this? Views claims they will do their update

I cant remove classy from 10.3. If I do, I get
Undefined array key "classy" ThemeHandler.php:74

It is not installed on my appearance page either.

So how do I get a D11 version?

https://www.drupal.org/project/webform/I → am confused by this long issue. How do I get webform to work on Drupal 11?

 # composer require "drupal/webform:dev-3465838-drupal-11-compatibility as 6.3.x-dev" -W
./composer.json has been updated
Running composer update drupal/webform --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
    - Root composer.json requires drupal/webform dev-3465838-drupal-11-compatibility as 6.3.x-dev, it is satisfiable by drupal/webform[dev-3465838-drupal-11-compatibility] from vcs repo (git https://git.drupalcode.org/issue/webform-3465838.git) but drupal/webform[dev-4.x, dev-5.x, dev-6.x, dev-6.0.x, dev-6.1.x, dev-6.2.x, dev-6.3.x, 4.x-dev (alias of dev-4.x), 5.0.0-beta1, ..., 5.x-dev (alias of dev-5.x), 6.0.0-alpha1, ..., 6.x-dev (alias of dev-6.x)] from composer repo (https://packages.drupal.org/8) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 2
    - drupal/webform_views is locked to version 5.4.0 and an update of this package was not requested.
    - drupal/webform_views 5.4.0 requires drupal/webform ^6.0 -> found drupal/webform[dev-6.x, dev-6.0.x, dev-6.1.x, dev-6.2.x, dev-6.3.x, 6.0.0-alpha1, ..., 6.x-dev (alias of dev-6.x)] but it conflicts with your root composer.json require (dev-3465838-drupal-11-compatibility as 6.3.x-dev).

and

# composer require drupal/webform:dev-3465838-drupal-11-compatibility
./composer.json has been updated
Running composer update drupal/webform
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/webform dev-3465838-drupal-11-compatibility, it is satisfiable by drupal/webform[dev-3465838-drupal-11-compatibility] from vcs repo (git https://git.drupalcode.org/issue/webform-3465838.git) but drupal/webform[dev-4.x, dev-5.x, dev-6.x, dev-6.0.x, dev-6.1.x, dev-6.2.x, dev-6.3.x, 4.x-dev (alias of dev-4.x), 5.0.0-beta1, ..., 5.x-dev (alias of dev-5.x), 6.0.0-alpha1, ..., 6.x-dev (alias of dev-6.x)] from composer repo (https://packages.drupal.org/8) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 2
    - drupal/webform_views is locked to version 5.4.0 and an update of this package was not requested.
    - drupal/webform_views 5.4.0 requires drupal/webform ^6.0 -> found drupal/webform[dev-6.x, dev-6.0.x, dev-6.1.x, dev-6.2.x, dev-6.3.x, 6.0.0-alpha1, ..., 6.x-dev (alias of dev-6.x)] but it conflicts with your root composer.json require (dev-3465838-drupal-11-compatibility).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Please issue a real release ASAP.

# composer require drupal/geolocation_geometry_natural_earth_us_states
./composer.json has been updated
Running composer update drupal/geolocation_geometry_natural_earth_us_states
Loading composer repositories with package information
Updating dependencies
Lock file operations: 4 installs, 0 updates, 0 removals
  - Locking drupal/geolocation_geometry (3.14.0)
  - Locking drupal/geolocation_geometry_data (4.0.0-alpha7)
  - Locking drupal/geolocation_geometry_natural_earth_us_states (4.0.0-alpha1)
  - Locking drupal/migrate_plus (6.0.4)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 4 installs, 0 updates, 0 removals
  - Syncing drupal/migrate_plus (6.0.4) into cache
  - Installing drupal/geolocation_geometry (3.14.0)
  - Installing drupal/migrate_plus (6.0.4): Cloning 6.0.4 from cache
  - Installing drupal/geolocation_geometry_data (4.0.0-alpha7)
  - Installing drupal/geolocation_geometry_natural_earth_us_states (4.0.0-alpha1)
2 package suggestions were added by new dependencies, use `composer suggest` to see details.
Package wikimedia/composer-merge-plugin is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
98 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
phpstan/extension-installer: Extensions installed
No security vulnerability advisories found.
Using version ^4.0@alpha for drupal/geolocation_geometry_natural_earth_us_states
jarfx:/srv/www/htdocs/www # drush updb
 [error]   (Currently using Missing or invalid module The following module is marked as installed in the core.extension
configuration, but it is missing:
 * geolocation_geometry_natural_earth_us_states

But again, drush does not see it:

www # ./dr pm-list | grep geolocation
  Geolocation                       Geolocation (geolocation)                                                              Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Address (geolocation_address)                                            Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Baidu Maps (geolocation_baidu)                                           Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Bing Maps (geolocation_bing)                                             Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Demo (geolocation_demo)                                                  Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Geocodio (geolocation_geocodio)                                          Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Geofield Integration (geolocation_geofield)                              Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Geometry (geolocation_geometry)                                          Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Geometry - Data (geolocation_geometry_data)                              Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Geometry - Demo (geolocation_geometry_demo)                              Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Google Maps API (geolocation_google_maps)                                Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Google Maps API - Demo (geolocation_google_maps_demo)                    Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Google Places API (geolocation_google_places_api)                        Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Google Static Maps (geolocation_google_static_maps)                      Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Google  Static Maps - Demo (geolocation_google_static_maps_demo)         Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - GPX (geolocation_gpx)                                                    Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Here Maps (geolocation_here)                                             Enabled    4.0.0-alpha7
  Geolocation                       Geolocation - Leaflet (geolocation_leaflet)                                            Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Leaflet - Demo (geolocation_leaflet_demo)                                Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Search API Integration (geolocation_search_api)                          Disabled   4.0.0-alpha7
  Geolocation                       Geolocation - Yandex Maps (geolocation_yandex)                                         Disabled   4.0.0-alpha7

Close this. Forgot to enable it. (needs to be in instructions)

tjtj → created an issue.

 The process "git clone --no-checkout '/root/.cache/composer/vcs/https---github.com-phpstan-phpstan.git/' '/   
 srv/www/htdocs/www/vendor/phpstan/phpstan' --dissociate --reference '/root/.cache/composer/vcs/https---gith   
 ub.com-phpstan-phpstan.git/' && cd '/srv/www/htdocs/www/vendor/phpstan/phpstan' && git remote set-url origi   
 n -- 'https://github.com/phpstan/phpstan.git' && git remote add composer -- 'https://github.com/phpstan/php   
 stan.git'" exceeded the timeout of 300 seconds.                                                               
                                                   
 

I get this too. My Config menu has disappeared, and when I manually go to admin/config, I get "access denied"
Path: /admin/config. Drupal\Core\Http\Exception\CacheableAccessDeniedHttpException: in Drupal\Core\Routing\AccessAwareRouter->checkAccess() (line 115 of /home/myname/public_html/mysite/web/core/lib/Drupal/Core/Routing/AccessAwareRouter.php).
I am admin. How do I track this down?

It was due to not using oAuth. The error message could be clearer.

Error got munged:
Warning: Undefined variable $send_test_link in
Drupal\mailchimp_campaign\Controller\MailchimpCampaignController->overview() (line 178 of
/home/stelnews/public_html/web/modules/contrib/mail

tjtj → created an issue.

I get this error too. And it kills Drush! This is critical.

Installed patch. seems to work. Thanks. This also solves the issues with the cheditor5_font plugin https://www.drupal.org/project/drupal/issues/3457622#comment-15664592 🐛 logic exception in Drupal\Core\Config\Schema\Mapp Postponed: needs info

Make a patch file and I will.

tjtj → created an issue.

I was unable to rename the title. But 10.3 checks the validity of CKEditor5 plugins, and this module failsw and prevents ant editing of a site. I had 5 sites affected by this, and all revived when I uninstalled this module.

17:07:05.068

Uncaught TypeError: can't access property "id", [].find(...) is undefined

Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist.

Oops. That is Drupal 10.3

tjtj → created an issue.

Bingo! Installing https://www.drupal.org/project/ckeditor5_font → throws this error!

uninstalling it removes the error. I am filing this with that project.

I uninstalled every CKEditor5 plugin and CKEditor itself (having removed CKEditor from the full_html and basic_html content editors. 10.3 works, and the editor.editor files are gone from configuration exports. I will now enable stuff one at a time.

# grep -rnw './' -e "filter_settings"
./webform/src/Form/AdminConfig/WebformAdminConfigFormsForm.php:90:    $form['filter_settings'] = [
./webform/src/Form/AdminConfig/WebformAdminConfigFormsForm.php:96:    $form['filter_settings']['limit'] = [
./webform/src/Form/AdminConfig/WebformAdminConfigFormsForm.php:111:    $form['filter_settings']['filter_category'] = [
./webform/src/Form/AdminConfig/WebformAdminConfigFormsForm.php:120:    $form['filter_settings']['filter_state'] = [
./slick/config/schema/slick.schema.yml:310:filter_settings.slick_filter:
./blazy/config/schema/blazy.schema.yml:163:filter_settings.blazy_filter:

Would uninstalling and reinstalling ckeditor5 fix this?
Would I need to uninstall all the plugins too, or is just changing all content types to text editor?

as per mortona2k, I searched all my modules
/web/modules/contrib # grep -rnw ./ -e "type: filter"
and got no hits.

Which modules?
CKEditor Find/Replace
This plugin module adds the find and replace dialog to CKEditor 5 in Drupal 9 or 10

  `ckeditor5.plugin.ckeditor5_list:properties` is invalid: its `label`
                                               key contains a string. It must be an array. in
                                               Drupal\Core\Config\Schema\Mapp

I did find nbsp installed and used in Full_HTML. I downgraded core, removed its use, uninstalled it, removed it, upgraded core, and got the same error.
ckeditor5_list is unchanged. I then uninstalled ckeditor_link_styles since most of the entries in ckeditor5_list see3med to be in ckeditor_link_styles_linkStyles. But they are still in editor.editor.full_html.yml even after removing the module.
Here is the whole file:

uuid: 01223bde-4b60-44eb-bcad-d906f3860401
langcode: en
status: true
dependencies:
  config:
    - filter.format.full_html
  module:
    - ckeditor5
format: full_html
editor: ckeditor5
settings:
  toolbar:
    items:
      - heading
      - sourceEditing
      - bold
      - italic
      - fontBackgroundColor
      - fontColor
      - fontFamily
      - link
      - fontSize
      - findAndReplace
      - imce_link
      - drupalInsertImage
      - imce_image
      - blockQuote
      - codeBlock
      - bulletedList
      - numberedList
      - horizontalLine
      - alignment
      - SimpleAds
      - '-'
      - insertTable
      - indent
      - outdent
      - lineHeight
      - drupalMedia
      - specialCharacters
      - openai
  plugins:
    ckeditor5_alignment:
      enabled_alignments:
        - center
        - justify
        - left
        - right
    ckeditor5_codeBlock:
      languages:
        -
          label: 'Plain text'
          language: plaintext
        -
          label: C
          language: c
        -
          label: 'C#'
          language: cs
        -
          label: C++
          language: cpp
        -
          label: CSS
          language: css
        -
          label: Diff
          language: diff
        -
          label: HTML
          language: html
        -
          label: Java
          language: java
        -
          label: JavaScript
          language: javascript
        -
          label: PHP
          language: php
        -
          label: Python
          language: python
        -
          label: Ruby
          language: ruby
        -
          label: TypeScript
          language: typescript
        -
          label: XML
          language: xml
    ckeditor5_font_colors:
      colors: '[{"color":"#000000","label":""},{"color":"#0432ff","label":""},{"color":"#aa7941","label":""},{"color":"#00fcff","label":""},{"color":"#00f900","label":""},{"color":"#ff40ff","label":""},{"color":"#ff9200","label":""},{"color":"#932092","label":""},{"color":"#ff2600","label":""},{"color":"#fefb00","label":""},{"color":"#feffff","label":""},{"color":"#949494","label":"Gray"}]'
    ckeditor5_heading:
      enabled_headings:
        - heading1
        - heading2
        - heading3
        - heading4
        - heading5
        - heading6
    ckeditor5_imageResize:
      allow_resize: true
    ckeditor5_line_height_line_height:
      line_height_options:
        - '0'
        - '0.5'
        - '1'
        - '1.5'
        - '2'
        - '2.5'
        - '3'
        - '3.5'
        - '4'
        - '4.5'
        - '5'
        - '5.5'
        - '6'
        - '6.5'
    ckeditor5_list:
      properties:
        reversed: true
        startIndex: true
      multiBlock: true
    ckeditor5_plugin_pack_font__font_color:
      colors: {  }
      use_default_colors: true
    ckeditor5_plugin_pack_font__font_family:
      options: ''
    ckeditor5_plugin_pack_font__font_size:
      options: ''
    ckeditor5_sourceEditing:
      allowed_tags: {  }
    ckeditor_link_styles_linkStyles:
      styles:
        -
          label: 'Button color: Primary'
          element: '<a class="button primary">'
        -
          label: 'Button color: Secondary'
          element: '<a class="button secondary">'
        -
          label: 'Button color: Success'
          element: '<a class="button success">'
        -
          label: 'Button color: Alert'
          element: '<a class="button alert">'
        -
          label: 'Button color: Warning'
          element: '<a class="button warning">'
        -
          label: 'Button size: Tiny'
          element: '<a class="button tiny">'
        -
          label: 'Button size: Small'
          element: '<a class="button small">'
        -
          label: 'Button size: Large'
          element: '<a class="button large">'
        -
          label: 'Button style: Expanded'
          element: '<a class="button expanded">'
        -
          label: 'Button style: Hollow'
          element: '<a class="button hollow">'
        -
          label: 'Button style: Clear'
          element: '<a class="button clear">'
        -
          label: 'Button style: Disabled'
          element: '<a class="button disabled">'
    media_media:
      allow_view_mode_override: true
    openai_ckeditor_openai:
      completion:
        enabled: true
        model: gpt-3.5-turbo
        temperature: 0.2
        max_tokens: 512
image_upload:
  status: true
  scheme: public
  directory: inline-images
  max_size: ''
  max_dimensions:
    width: 0
    height: 0

Sorry. Explain was not needed. Saying it was in site export would have helped. But this list is in the three attached files.

sh-3.2# grep -rnw './config-orcma-dyndns-org-2024-06-29-15-19/' -e "ckeditor5_list"
./config-orcma-dyndns-org-2024-06-29-15-19//editor.editor.basic_html.yml:73: ckeditor5_list:
./config-orcma-dyndns-org-2024-06-29-15-19//editor.editor.full_html.yml:122: ckeditor5_list:
./config-orcma-dyndns-org-2024-06-29-15-19//editor.editor.webform_default.yml:42: ckeditor5_list:

So what is wrong?

  ckeditor5_list:
      properties:
        reversed: true
        startIndex: true
      multiBlock: true
    ckeditor5_plugin_pack_font__font_color:
      colors: {  }
      use_default_colors: true
    ckeditor5_plugin_pack_font__font_family:
      options: ''
    ckeditor5_plugin_pack_font__font_size:
      options: ''
    ckeditor5_sourceEditing:
      allowed_tags: {  }
    ckeditor_link_styles_linkStyles:
      styles:
        -
          label: 'Button color: Primary'
          element: '<a class="button primary">'
        -
          label: 'Button color: Secondary'
          element: '<a class="button secondary">'
        -
          label: 'Button color: Success'
          element: '<a class="button success">'
        -
          label: 'Button color: Alert'
          element: '<a class="button alert">'
        -
          label: 'Button color: Warning'
          element: '<a class="button warning">'
        -
          label: 'Button size: Tiny'
          element: '<a class="button tiny">'
        -
          label: 'Button size: Small'
          element: '<a class="button small">'
        -
          label: 'Button size: Large'
          element: '<a class="button large">'
        -
          label: 'Button style: Expanded'
          element: '<a class="button expanded">'
        -
          label: 'Button style: Hollow'
          element: '<a class="button hollow">'
        -
          label: 'Button style: Clear'
          element: '<a class="button clear">'
        -
          label: 'Button style: Disabled'
          element: '<a class="button disabled">'
    media_media:
      allow_view_mode_override: true
    openai_ckeditor_openai:
      completion:
        enabled: true
        model: gpt-3.5-turbo
        temperature: 0.2
        max_tokens: 512

See uploaded files. If you had been more specific in your instructions, I would have provided them days ago.

Where are these files?

I have never needed it before. The upgrade to 10.3 wronked all my sites. I do not see what the configuration system does for this, nor how to use it. Updating core should not do this to me. So yes, some more hints please.
Was ckeditor5.ckeditor5.yml the correct file? What is wrong with it?