🇹🇷Turkey @orkut murat yılmaz

@pearls, I do agree with you. Should I contact one of the maintainers?

I can also confirm that too. Thank you @benjifisher :)

Sorry, I forgot saying that, I've applied the MR as a patch and scanned entity limit with upgrade status module:

No problems found

any chance for applying this to 4.x?

@pearls, can you review the @jdvc's MR too?

I've just tested the latest version and it looks stable.

Thanks for all the efforts:)

any chance for merge?

any chance for merge?

@rakesh.gectcr, thanks for the patch. I can confirm that, patch #49 can fix this issue too.

any chance for merge?

@vinodhini.e thanks for all the tests:)

@vinodhini.e great:)

@vinodhini.e thank you:)

It will be fixed, if the MR of this issue 💬 Please develop the module for Drupal 10 Active is accepted.

Please consider my issue ✨ Disable email field on user registration form, if it is set as optional Active too. :)

@vinodhini.e, can you also test these issues too?

https://www.drupal.org/project/optional_email/issues/3530927 ✨ Disable email field on user registration form, if it is set as optional Active

https://www.drupal.org/project/optional_email/issues/3443982 💬 Please develop the module for Drupal 10 Active

if they work for you too, please change the status as RTBC for both of them:)

I've just re-scanned the module with the patch applied, using upgrade status module and there is an error, preventing the upgrade, which I paste below:

file: web/modules/contrib/faq/faq.install

line: 59

error: Relying on entity queries to check access by default is deprecated in drupal:9.2.0 and an error will be thrown from drupal:10.0.0. Call \Drupal\Core\Entity\Query\QueryInterface::accessCheck() with TRUE or FALSE to specify whether access should be checked.

I'm changing the issue's status as "needs work".

Can you review my MR please?

orkut murat yılmaz → created an issue.

@drupal.ninja03, I've tested your patch and it is working. Thanks for your contribution:)

The patch does not work. @sandeep_jangra

I've created a Merge Request, using Upgrade Status module → 's scanning function. It works on my development and test environments.

Can you review it please?

the patch #28 works great:)

any updates?

@jurgenhaas, thanks for your kind and quick answer:)

The error is gone, when I switched to dev version.

any chance for merge?

orkut murat yılmaz → created an issue.

@jfeltkamp, thanks for the patch. I works well:)

Also, problem still exists with cookies 2.0.0-alpha3 (and 2.x-dev) too.

I've updated my Drupal core to 11.2.0-rc2 today, but the problem doesn't disappear.

The changeset looks mergeable.

It's not directly related to this issue, but this blog post has given some ideas to me:

https://www.gomomento.com/blog/valkey-turns-one-how-the-community-fork-l...

After a few cache clear and drush updb, upgrade to Webform 6.3 went well. I'm closing this issue.

Thanks for everything.

Sorry for the previous message.

I've just tested the MR as a patch and scanned with Upgrade Status module. The result is:

There is an error in user_one_time_login/src/Form/UserOneTimeLoginConfigForm.php file, line 36:

Call to deprecated function user_role_names(). Deprecated in drupal:10.2.0 and is removed from drupal:11.0.0. Use Drupal\user\Entity\Role::loadMultiple() and, if necessary, an inline implementation instead.

orkut murat yılmaz → created an issue.

any updates on this?

This is the output of the audit command:

composer audit
Found 1 security vulnerability advisory affecting 1 package:
+-------------------+----------------------------------------------------------------------------------+
| Package           | drupal/faq                                                                       |
| Severity          |                                                                                  |
| CVE               | NO CVE                                                                           |
| Title             | Frequently Asked Questions - Critical - Unsupported - SA-CONTRIB-2019-077        |
| URL               | https://www.drupal.org/sa-contrib-2019-077                                       |
| Affected versions | *                                                                                |
| Reported at       | 2019-11-13T18:00:36+00:00                                                        |
| Advisory ID       | SA-CONTRIB-2019-077                                                              |
+-------------------+----------------------------------------------------------------------------------+

Thanks for the merge:)

@ressa, thanks for the improvement:)

orkut murat yılmaz → created an issue.

thanks for the merge:)

any updates on this?

Sorry, I forgot doing "drush updb" after the update.

orkut murat yılmaz → created an issue.

The MR 21 works:)

@greg boggs thanks for refactoring and the missing comments too:)

any chance for review?

Thanks for the merge:)

any chance for merge?

any chance for merge?

any chance for the merge?

Can someone test and review this?

It is a little commit, but looks working. Can someone review and test it too?

orkut murat yılmaz → created an issue.

any updates?

@axelm, thanks for correcting my mistake, D10 support will be over in a year.

It is very interesting that the status of this issue has remained as "Needs review" for 6 months. Also, Drupal 10's support will be over in 6 months.

The feeling of abandonment is a heavy burden to carry for everyone.

We need to analyze this case carefully and find out what can be done for the benefit of our community.

I've created an MR, with the help of ollama and gemma3 :)

Can you review it please?

@andeersg, any chance for reviewing this issue too?

@andeersg, thank you:)

This is my upgrade status output, after applying the latest MR as a patch:

ddev drush us-a phone_number          

================================================================================
Phone Number,  2.0.0-alpha7
Scanned on Mon, 03/24/2025 - 10:50

FILE: web/modules/contrib/phone_number/src/Element/PhoneNumber.php

STATUS         LINE                           MESSAGE                           
--------------------------------------------------------------------------------
Ignore         36   Class Drupal\phone_number\Element\PhoneNumber extends       
                    deprecated class Drupal\Core\Render\Element\FormElement.    
                    Deprecated in drupal:10.3.0 and is removed from             
                    drupal:12.0.0. use                                          
                    Drupal\Core\Render\Element\FormElementBase instead.         
--------------------------------------------------------------------------------

FILE:
web/modules/contrib/phone_number/modules/sms_phone_number/src/Element/SmsPhoneNu
mber.php

STATUS         LINE                           MESSAGE                           
--------------------------------------------------------------------------------
Check manually 103  The 'sms_phone_number/element' library is not defined       
                    because the defining extension is not installed. Cannot     
                    decide if it is deprecated or not.                          
--------------------------------------------------------------------------------

I've tested the patch on my local and it works:)

Sorry, my bad. It's working. Keep calm and clear the cache:)

orkut murat yılmaz → created an issue.

orkut murat yılmaz → created an issue.

When I try to run cron or update the translations, I receive the error below:

TypeError: fgets(): Argument #1 ($stream) must be of type resource, false given in fgets() (line 248 of /var/www/html/web/core/lib/Drupal/Component/Gettext/PoStreamReader.php).

I guess, it is related to this error.

any chance for merge?

Hello @aleix,

Sorry, I haven't noticed the 2.x version. I'm going to try it very soon. I also have starred Map Libre modules, those are needed for Drupal community as well:) I've sent a message via your contact form too:)

Thanks for all:)

Any updates?

Today a new release → is created for Entity Usage. After that, this is the output:

$ ddev composer up -W                          
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 2 updates, 0 removals
  - Upgrading drupal/entity_usage (2.0.0-beta22 => 2.0.0-beta23)
  - Upgrading drupal/views_dependent_filters (dev-1.x 56e4a2d => 1.3.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 2 updates, 0 removals
  - Downloading drupal/entity_usage (2.0.0-beta23)
  - Syncing drupal/views_dependent_filters (1.3.0) into cache
  - Upgrading drupal/entity_usage (2.0.0-beta22 => 2.0.0-beta23): Extracting archive
  - Upgrading drupal/views_dependent_filters (dev-1.x 56e4a2d => 1.3.0): Checking out 8.x-1.3 from cache
Generating autoload files
67 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.

This is what I see:

$ ddev composer require 'drupal/views_dependent_filters:^1.3' --no-update
./composer.json has been updated
$ ddev composer update --dry-run                                         
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 2 updates, 0 removals
  - Upgrading drupal/entity_usage (2.0.0-beta21 => 2.0.0-beta22)
  - Locking drupal/views_dependent_filters (dev-1.x 56e4a2d)
  - Upgrading phpstan/phpstan (1.12.20 => 1.12.21)
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 2 updates, 0 removals
  - Upgrading drupal/entity_usage (2.0.0-beta21 => 2.0.0-beta22)
  - Upgrading phpstan/phpstan (1.12.20 => 1.12.21)
  - Installing drupal/views_dependent_filters (dev-1.x 56e4a2d)
67 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
$ ddev composer update          
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 2 updates, 0 removals
  - Upgrading drupal/entity_usage (2.0.0-beta21 => 2.0.0-beta22)
  - Locking drupal/views_dependent_filters (dev-1.x 56e4a2d)
  - Upgrading phpstan/phpstan (1.12.20 => 1.12.21)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 2 updates, 0 removals
  - Downloading drupal/entity_usage (2.0.0-beta22)
  - Syncing drupal/views_dependent_filters (dev-1.x 56e4a2d) into cache
  - Upgrading drupal/entity_usage (2.0.0-beta21 => 2.0.0-beta22): Extracting archive
  - Upgrading phpstan/phpstan (1.12.20 => 1.12.21): Extracting archive
  - Installing drupal/views_dependent_filters (dev-1.x 56e4a2d): Cloning 56e4a2de04 from cache
Generating autoload files
67 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.

orkut murat yılmaz → created an issue.

orkut murat yılmaz → created an issue.

I've applied the @arunkumark's MR as a patch and I confirm that I can delete the related field now.

Sorry @emulamba, it was my bad. I've done the necessary things.

Thanks for your contribution:)

@generalredneck, any chance for merge?

Sorry, closing this duplicate issue.

@emulamba, thanks for the commit, but can you correct your MR please? We need it to be merged with 3.0.0-rc1 version.

It looks beautiful on live demo and if I can find a chance to test it locally, I'll update this issue. :)

Sorry for very late reply, it is solved with setting the dimensions of the custom icons.

Thanks for everything:)

@vandana, there is a conflict in your MR. can you resolve it and then update your MR please?

I think the correct project for the issue is SMS Framework. Having a similar error, as I paste below:

Drupal\sms\Exception\SmsPluginReportException: Missing reports for 1 recipient(s). in Drupal\sms\EventSubscriber\SmsMessageProcessor->ensureReports() (line 122 of /var/www/html/web/modules/contrib/smsframework/src/EventSubscriber/SmsMessageProcessor.php).

What could be the reason?

Best,
Orkut

any chance for merge?

Any updates?

@dench0 can you reactivate this issue?

orkut murat yılmaz → created an issue.

Hello again,

Thanks for all the things you do:)

Can you update module info page and the issue summary too?

Best,
Orkut

any updates?

Any updates?

Thanks for the patch.