@vpa24

Stable 9 uses from both Drupal 9 and Drupal 10 not only Drupal 9.

Change foo.settings.yml:

from foo_example: blue bikeshed to foo_example: 'blue bikeshed'

added Twig include link's documentation

improved format

Added Password Policy module

Improve format

Added a link of instruction for hook_update_N

Adding clear cache by using drush cr

Changed the title from Step #1: Define hook_theme in .module file to Step #1: Define hook_theme() in .module file

Added Tailwindcss

vpa24 → changed the visibility of the branch 3157921-support-for-cors to hidden.

vpa24 → changed the visibility of the branch 3157921-support-for-cors to hidden.

vpa24 → made their first commit to this issue’s fork.

Adding Drupal and YAML extentions

improving set_attribute's content

improving format

adding add_class and set_attribute filter

changed code format for raw filter

Adding example for raw filter

Adding Twig document links for Drupal 8.x, Drupal 9.x, and Drupal 10.x

We can't using Composer to download Drupal 7.

fixed one small grammar mistake

Added Drupal 9 and 10 on the Contex section.

We can't download Drupal core project via drush dl → since Drush 9. I added Drupal 9 and Drupal 10 on the "Using Composer to manage Drupal dependencies".

I changed "module"/snippets/src/Plugin/Field/FieldType/SnippetsItem.php to modules/custom/snippets/src/Plugin/Field/FieldType/SnippetsItem.php because the directory structure will be clearer.

I changed from core: 8.x  to core_version_requirement: ^9 || ^10  in the Attaching libraries from your theme's info.yml section because core: 8.x syntax was deprecated starting since Drupal version 8.7.7.

Hello everyone, I am currently using the Password Policy module version 4.0.0. By default, there is a field named "Password Expiration" on each user edit page, and this field is checked, meaning that passwords will expire for these users. Therefore, I believe there's no need to add a "Password never expires" field. Instead, I have implemented bulk actions to allow for the direct checking or unchecking of this field from the "People" view.

Hello everyone, I am currently using the Password Policy module version 4.0.0. By default, there is a field named "Password Expiration" on each user edit page, and this field is checked, meaning that passwords will expire for these users. Therefore, I believe there's no need to add a "Password never expires" field. Instead, I have implemented bulk actions to allow for the direct checking or unchecking of this field from the "People" view.

Thanx @yashsharma01 for patch, Patch #10 🐛 TypeError - get_class_methods - php > 8 (drupal 10) RTBC works for me.

Hello @bnjmnm, I think we can't use both visibility: hidden; and display: none; together doesn't make sense, as they serve similar purposes of hiding elements but in different ways.

When you use visibility: hidden; the element becomes invisible, but it still occupies space on the page. On the other hand, when you use display: none; the element is completely removed from the layout.

Thanks, @jennypanighetti, I created a new patch to address the issue.

It works with `drupal/core-recommended` 10.1.1 by using this command `composer require 'drupal/s3fs:^3.3' -W`

Hello everyone, I am using Drupal 10.1 but I still can not install this module and I don't know how to solve this issue. Any other solutions? Thanks.

vpa24 → made their first commit to this issue’s fork.

Hi, this path works for the latest version of this module.

I still got an error in Drupal 10 even though I updated these patch above

Drupal\Core\Entity\Query\QueryException: Entity queries must explicitly set whether the query should be access checked or not. See Drupal\Core\Entity\Query\QueryInterface::accessCheck(). in Drupal\Core\Entity\Query\Sql\Query->prepare() (line 141 of core/lib/Drupal/Core/Entity/Query/Sql/Query.php).
Drupal\Core\Entity\Query\Sql\Query->execute() (Line: 105)
Drupal\eck\Controller\EckEntityTypeListBuilder->buildRow(Object) (Line: 219)
Drupal\Core\Entity\EntityListBuilder->render() (Line: 23)
Drupal\Core\Entity\Controller\EntityListController->listing('eck_entity_type')
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 163)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 74)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 686)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

I fixed and tested all of the issues Call to deprecated method getImplementations() of class Drupal\Core\Extension\ModuleHandlerInterface. Deprecated in drupal:9.4.0 and is removed from drupal:10.0.0. Instead you should use ModuleHandlerInterface::invokeAllWith() for hook invocations or you should use ModuleHandlerInterface::hasImplementations() to determine if hooks implementations exist.

There is a small issue for the release version 2.x-dev
Drupal\Core\Extension\InfoParserException: The 'core_version_requirement' constraint (^9.3 || ^10) requires the 'core' key not be set in modules/contrib/bricks/modules/bricks_paragraphs/bricks_paragraphs.info.yml in Drupal\Core\Extension\InfoParserDynamic->parse() (line 88 of core\lib\Drupal\Core\Extension\InfoParserDynamic.php).

I still have the same error when I updated this module for a D10 release

PHP Fatal error:  Declaration of Drupal\csv_serialization\Encoder\CsvEncoder::encode($data, string $format, array $context = []): string must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode($data, $format, array $context = []) in C:\work\drupal10\web\modules\contrib\csv_serialization\src\Encoder\CsvEncoder.php on line 125
 [warning] Drush command terminated abnormally.

When will we have a new release for this module that is compatible with Drupal 10?

Fixed that errors
Call to deprecated method getImplementations() of class Drupal\Core\Extension\ModuleHandlerInterface. Deprecated in drupal:9.4.0 and is removed from drupal:10.0.0. Instead you should use ModuleHandlerInterface::invokeAllWith() for hook invocations or you should use ModuleHandlerInterface::hasImplementations() to determine if hooks implementations exist.

From a recent test by Upgrade Statuc:
Call to deprecated method getImplementations() of class Drupal\Core\Extension\ModuleHandlerInterface. Deprecated in drupal:9.4.0 and is removed from drupal:10.0.0. Instead you should use ModuleHandlerInterface::invokeAllWith() for hook invocations or you should use ModuleHandlerInterface::hasImplementations() to determine if hooks implementations exist.

From a recent test by Upgrade Statuc:
`Call to deprecated method getImplementations() of class Drupal\Core\Extension\ModuleHandlerInterface. Deprecated in drupal:9.4.0 and is removed from drupal:10.0.0. Instead you should use ModuleHandlerInterface::invokeAllWith() for hook invocations or you should use ModuleHandlerInterface::hasImplementations() to determine if hooks implementations exist.`

This patch worked for version 2.0.3