🇹🇷Turkey @orkut murat yılmaz

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.

Any updates on this?

any chance for merge?

Thanks for the add:)

orkut murat yılmaz → created an issue.

Hello and thanks for the contributions,

Are you going to add Drupal 11 compatibility info to the module page?

Best,
Orkut

Any chance for review?

Thanks for your efforts:)

@matsbla, thanks for the fix and new release too:)

I've tested @immaculatexavier's MR as a patch and it works.

Thanks for contributions.

Any updates on this?

Congratulations @oscarnovasf :)

When I updated my core with drupal 10.4.x-dev, I start reaching to my web interface and all the errors become warnings. After rebuilding the cache, warnings disappear, as told on comment #2.

When check the browser, I see the WSOD, with the full error message below:

The website encountered an unexpected error. Try again later.
Error: Class "Doctrine\Deprecations\Deprecation" not found in Doctrine\Common\Lexer\Token->offsetGet() (line 104 of /var/www/html/vendor/doctrine/lexer/src/Token.php).

Doctrine\Common\Lexer\Token->offsetGet() (Line: 619)
Drupal\Component\Annotation\Doctrine\DocParser->Annotations() (Line: 338)
Drupal\Component\Annotation\Doctrine\DocParser->parse() (Line: 101)
Drupal\Component\Annotation\Doctrine\SimpleAnnotationReader->getClassAnnotations() (Line: 125)
Drupal\Component\Annotation\Doctrine\SimpleAnnotationReader->getClassAnnotation() (Line: 145)
Drupal\Component\Annotation\Plugin\Discovery\AnnotatedClassDiscovery->getDefinitions() (Line: 119)
Drupal\Core\Entity\EntityTypeManager->findDefinitions() (Line: 213)
Drupal\Core\Plugin\DefaultPluginManager->getDefinitions() (Line: 22)
Drupal\Core\Plugin\DefaultPluginManager->getDefinition() (Line: 135)
Drupal\Core\Entity\EntityTypeManager->getDefinition() (Line: 260)
Drupal\Core\Entity\EntityTypeManager->getHandler() (Line: 195)
Drupal\Core\Entity\EntityTypeManager->getStorage() (Line: 42)
Drupal\eca\Token\CurrentUserDataProvider->__construct() (Line: 261)
Drupal\Component\DependencyInjection\Container->createService() (Line: 179)
Drupal\Component\DependencyInjection\Container->get() (Line: 438)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters() (Line: 275)
Drupal\Component\DependencyInjection\Container->createService() (Line: 179)
Drupal\Component\DependencyInjection\Container->get() (Line: 438)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters() (Line: 239)
Drupal\Component\DependencyInjection\Container->createService() (Line: 179)
Drupal\Component\DependencyInjection\Container->get() (Line: 438)
Drupal\Component\DependencyInjection\Container->resolveServicesAndParameters() (Line: 239)
Drupal\Component\DependencyInjection\Container->createService() (Line: 179)
Drupal\Component\DependencyInjection\Container->get() (Line: 105)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch() (Line: 239)
Symfony\Component\HttpKernel\HttpKernel->handleThrowable() (Line: 91)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 50)
Drupal\ban\BanMiddleware->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 741)
Drupal\Core\DrupalKernel->handle() (Line: 19)

orkut murat yılmaz → created an issue.

orkut murat yılmaz → created an issue.

Thanks for this feature:)

It still exists with the version 8.x-1.34.

Hello all,

I've just created an issue ✨ Merge with "Openlayers 6" project Active , about project merge.

Best,
Orkut

orkut murat yılmaz → created an issue.

Also, I've tried it with Drupal 11, PHP 8.3 and PostgreSQL 17 :)

Thank you @Oulalahakabu for the new version. I've tried it with the new one and it works so nice.

@saurabhkanva, thanks for the patch:)

As I said before, I strongly do agree with @jcandan. This could be a good opportunity for community involvement.

I'd like to add that, Elastic's decision is inspirational. Please adopt it.

orkut murat yılmaz → created an issue.

Thanks for this wonderful work:)

th

Dear @damien laguerre, thank you for your beautiful effort:)

subscribing :)

@pobster, thanks for the merge:)

can we consider merging with the 4.1.1 release and publish it on the module project's page too?

best,
Orkut

I misunderstood your comment #3 @pobster, but it is more clear for me now.

Thanks for your contribution @the_g_bomb.

When I try to enable the module, after applying your commits as a patch, I receive the error message below:

Class "Symfony\Component\EventDispatcher\Event" not found

Thank you @itamair:)

Unfortunately, user interface translation doesn't accept translating HTML tags. I'm changing the issue's status.

I'm also uploading my commit as a patch file, in order to use it in my composer.json file, until it merges into stable branch.

I've added a simple "trans" function in the last part of the array. Can you check this one too?

@Tanushree Gupta, thanks for your contribution. However, your work does focus on translating the strings, already hard coded in the slider.html.twig file. It won't work with the "slider_code" variable.

@apaderno, you're right. Thanks for correcting.

Thank you @Berdir :)

If I change the content_sync.info.yml as below, upgrade status report says that, it is compatible with D11 too.

name: 'Content Sync'
type: module
description: 'Allows users to import/export content using YAML files.'
package: Custom
core_version_requirement: ^9.4 || ^10.0 || ^11
configure: content.sync
dependencies:
  - drupal:serialization 

# Information added by Drupal.org packaging script on 2022-12-23
version: '3.0.0-beta1+27-dev'
project: 'content_sync'
datestamp: 1671838601

Please publish the dev release with this changes:) I'm excited to put this in to my CI/CD flows:)

I've downloaded the 3.0.x-dev release, applied @mjgruta's latest MR (as a patch) and changed the content_sync.info.yml file like below:

name: 'Content Sync'
type: module
description: 'Allows users to import/export content using YAML files.'
package: Custom
core_version_requirement: ^9.4 || ^10.0
configure: content.sync
dependencies:
  - drupal:serialization 

# Information added by Drupal.org packaging script on 2022-12-23
version: '3.0.0-beta1+27-dev'
project: 'content_sync'
datestamp: 1671838601

And activated the module.

It works nice with Drupal 10.3.0-rc1, PHP 8.3.8 and PostgreSQL 16.1 :

Thank you for everything.

@bojanz, I meant 2.0.1 (or 2.0.2) as stable branch. Thanks for your fast response:)

from now on, I'll choose a wiser issue title like this:) thanks for your warning @ressa

@itamair, thanks for the release:)

I've added @balbeeryadav's patch to my composer.json file like this:

        "enable-patching": true,
        "patches": {
	    "drupal/facets": {
                "Facets 3.0.0-beta2 release?": "https://www.drupal.org/files/issues/2024-06-01/beta-dev-diff-3394709-6.patch"
            }
	}

But we need to commit all RTBC issues to the dev branch and then merge everything with the Beta2 release as well.

@W01F, should we include those differences as features to db_maintenance?

Orkut Murat Yılmaz → created an issue.

Sorry, I've missed the other one 📌 Initial Drupal 11 compatibility Fixed . Closing this duplicate issue.

Orkut Murat Yılmaz → created an issue.

It works locally:)

Any chance for merge?