🇫🇷France @laurent.lannoy

Sorry @tr for my late reply to your post #25
I was just expecting a minor version 2.2.1 which includes a test of the version of the module data into the current DB to know if it needs to be updated or not ... not for me (updates are done), but for those who don't have updated yet and to avoid them to lose time with an extra manual process. That's all :-)

Thanks @slown

It's just unfortunate that there is no reaction from maintainers on this thread, and by putting a new version correcting the problem for those who will update later.

Hi @sonfd

Is really probably missing quite a few steps for most people. I think most people update on a local environment and then deploy changes to development, test, and live environments. Note that you'll need to deploy 2.1.4 and run drush updb all the way to your live environment before updating to 2.2. - I updated the issue summary with this note.

I think it is what I already specified on my post #6, right ?

Hello,

Waiting for a corrective version, just force update to version 2.1.4 with the DB update, then update normaly ... and all is fine. You can do this even you previously update to 2.2.0

composer require 'drupal/honeypot:2.1.4'
drush updatedb
drush cr
composer require 'drupal/honeypot'
drush updatedb
drush cr

Same problem ! It appear only when not identified.
Downgrading to 2.1 solves the issue by now.

Thank you @ressa #12

Hello,
Sorry for my lack of experience in module development. Can you tell me where to put this function #10 to disable update notifications on this module please? Thank's

Hello,
has it not been fixed on v9.5.10 → - Issue #3270647 ???

The problem is the same using a pattern with pathauto module :

Using the following pattern to generate automatic URL for my event pages :
events/[node:field_smart_date:value-custom:Y-m-d]_[node:title]
The result for "My first event" is
events/_my-first-event
instead of
events/2023-11-17_my-first-event

Same problem with value-format:my-id into the pattern.

Only with Drupal 10 (10.1.6 tested) ... OK with Drupal 9 (9.5.11 tested)
Smart-date v4.0.3 or v4.1.0-rc3 ... same problem.

I had to downgrade to token:1.12 to fix the problem on all my websites.

See issue 🐛 Token with "value-custom:?" return an empty string Closed: works as designed

Yes ! It works with token:1.12.
Thanks a lot :)

laurent.lannoy → created an issue.

Thanks Squiggy.

This was my first install of an unsupported module.

I couldn't update, so I uninstalled leaflet_mapbox on D9 first, then updated the website to D10, then reinstalled leaflet_mapbox with the help of mglaman/composer-drupal-lenient and the patch #6.

Everything seems OK under Drupal 10 and I can visualize my map with my map defined in Mapbox and using the leaflet_mapbox module. 👍

Thank you @chucksimply for the "alpha1" version of the patch, the leaflet_mapbox.info.yml file has been successfully updated:

core_version_requirement: ^8.7.7 || ^9 || ^10

... but when I want to update the core version from 9.5.11 to 10.1.6, I got the following error message as the row had not been updated:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/leaflet_mapbox ^1.0@alpha -> satisfiable by drupal/leaflet_mapbox[1.0.0-alpha1].
    - drupal/leaflet_mapbox 1.0.0-alpha1 requires drupal/core ^8.7.7 || ^9 -> found drupal/core[8.7.7, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (^10).

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