🇮🇳India @pemson18

pemson18 → created an issue.

pemson18 → created an issue.

pemson18 → created an issue.

The `use_changed_timestamp` configuration setting should be moved to a configuration form, making it part of the module's settings. For checkout links, it is recommended that this configuration be global and not be overridden when calling the following method:

CheckoutLinkManager::generateUrl($order);

Additionally, the method:
public static function generateHash($timestamp, OrderInterface $commerce_order);

should be refactored to accept only two parameters. The value of `use_changed_timestamp` should then be retrieved from the module's configuration settings, rather than being passed as a parameter in the method call.

This approach ensures better consistency and flexibility by centralizing the configuration while simplifying the method signature.

For Admin users the user information is loaded by default which sometimes breaks the side due to records having info 20k+ users. The show "Term permission information on node edit page" overrides the config "Hide terms permissions information in the node form." for admin users which inturn break the page load on Users info 20k+ records

pemson18 → created an issue.

Hello Peter,
I have enabled the " Hide terms permissions information in the node form" setting in module settings. Also the permission by default has the been enabled for the admin user, The widget is display differently in the node edit form. It should have overridden the permission "Enables the specific role to see the term permissions on the node edit page" for the admin use and not display the users info in the edit form. Hope I am able to convey this issue properly.

Hello Peter, should the permission supersede the settings. Since for the admin user the permission is enabled by default and the setting "hide the terms info on node edit page" doesn't come into effect.

I stumbled upon the setting not working if the condition is set in the permissions_by_term setting form. added #13 patch for the same. Requesting Peter for reviewing the same...

pemson18 → created an issue.

Refactor Patch add schema and install definition and description fixes

pemson18 → created an issue. See original summary → .

goto the route admin/structure/webform/manage/{webform_name}/settings/form
Form access denied settings
check the option - Login (Redirects to user login form and displays message. Field, nodes, and block only display the message.)

pemson18 → created an issue. See original summary → .

Hi, Had this error on drush updb error log...

pemson18 → created an issue.

Note : The correct arguments passed in the services.yml in the custom or contrib module to the session limit should be 9 if you have a custom services decorator...

    arguments: ['@database', '@event_dispatcher', '@current_route_match', '@current_user', '@session_manager', '@module_handler', '@config.factory', '@messenger', '@logger.factory']

pemson18 → created an issue.

pemson18 → created an issue.

This is now fixed in the latest webform v6.2.7. doesn't require the patch. in your custom code 'category' needs to be replace to 'categories'

pemson18 → created an issue.

vendor/phpstan/phpstan/phpstan.phar
requires >= 8.3
seems like issue with this waz my cmd php v is 8.2

Pemson18 → created an issue.

Pemson18 → created an issue.

rm -rf vendor and contrib modules folder and then composer install back the vendor and contrib modules fixes this issue

I had to create a menu in the drupal admin backend ui and place it using the block layout admin section and then export it and in the menu link update the menu links for the menu in update hook. so its a mixture of ui config + update code not pure code.

Pemson18 → created an issue.

Pemson18 → created an issue.

fixed the link to reroute module

Pemson18 → created an issue.

Pemson18 → created an issue.

Try drush pmu shortcut

change uuid of config file shortcut.set.default.yml in your config dir to the current site uuid and then config import
 

To get current system site uuid

drush config-get "system.site" uuid

The CKEditor 4 still exists in the core extension and dependency is not yet transferred.
you can do composer require 'drupal/ckeditor:^1.0' to keep CKEditor
or change all CKEditor4 dependent config to ckeditor5 after enabling ckeditor5.

see https://www.drupal.org/project/drupal/issues/3130912 🐛 Incorrect Cache-Control headers for authenticated users Postponed

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

Pemson18 → created an issue.