🇮🇳India @mubasshir khan

Configure Session Storage in settings.php

Add the following lines to your settings.php file to configure Drupal to use Redis for session storage:

// Redis configuration.

$settings['redis.connection']['interface'] = 'PhpRedis';

$settings['redis.connection']['host'] = '127.0.0.1'; // Your Redis instance hostname.

$settings['redis.connection']['port'] = 6379; // Your Redis instance port.

$settings['redis.connection']['base'] = 101; // Redis database number.

// Use Redis for cache.

$settings['cache']['default'] = 'cache.backend.redis';

// Use Redis for session storage.

$settings['session_storage'] = [

'class' => 'Drupal\redis\Cache\PhpRedis',

'name' => 'session',

'bin' => 'sessions',

'prefix' => 'drupal:',

];

// Include the Redis services file.

$settings['container_yamls'][] = 'modules/contrib/redis/example.services.yml';

// Ensure the lock and cache tags bins are assigned to Redis.

$settings['cache']['bins']['form'] = 'cache.backend.database';

$settings['cache']['bins']['page'] = 'cache.backend.redis';

$settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.redis';

$settings['cache']['bins']['render'] = 'cache.backend.redis';

$settings['cache']['bins']['discovery'] = 'cache.backend.redis';

$settings['cache']['bins']['bootstrap'] = 'cache.backend.redis';

$settings['cache']['bins']['config'] = 'cache.backend.redis';

$settings['cache']['bins']['data'] = 'cache.backend.redis';

$settings['cache']['bins']['default'] = 'cache.backend.redis';

1 - Resolving the TypeError in the ai_api_explorer Module.
Make sure the right class is being used. You may need to change the service definition or the constructor to take the correct type.

Check the service definition in your module's services.yml file:

services:
  ai_api_explorer.image_and_audio_to_video_generator:
    class: Drupal\ai_api_explorer\Plugin\AiApiExplorer\ImageAndAudioToVideoGenerator
    arguments: ['@service_container', '@entity_type.manager', '@file_system', '@logger.factory', '@module_handler', '@path.alias_manager', '@renderer', '@file_url_generator']

Ensure that @file_url_generator is correctly defined and injected.

2 - Correcting the mistake in the commerce_license module.
Look at the checkUserHasExistingRights method in the Role class and make sure the entity is loaded correctly before using any methods on it.

<?php
public function checkUserHasExistingRights($user) {
  $role = $this->entityTypeManager->getStorage('user_role')->load($this->getRoleId());
  if ($role) {
    // Proceed with the logic
  } else {
    // Handle the case where the role is not found
    \Drupal::logger('commerce_license')->error('Role not found.');
  }
}

3 - Steps to Troubleshoot and Fix Issues
a. Backup Your Site
Always make sure to back up your site completely before making any updates or changes.

b. Update Dependencies
Check that all dependencies are current. Use the following commands:

c. Clear Cache
Clear the Drupal cache to make sure all changes are applied:

d. Run Database Updates
Execute the database updates to implement any outstanding updates:

e. Check for Custom Code
Examine any custom code or patches that could be causing issues. Verify that custom modules and themes work with the new version.

2. Rolling Back
If you need to revert to a previous version, restore both the codebase and the database to how they were before the upgrade attempt.

3. Consult Module Maintainers
If problems continue, consider contacting the maintainers of the contributed modules (like ai_api_explorer, commerce_license, etc.) for help. They may have specific fixes or updates to resolve these issues.

Please test the complete code below and ensure you have handled the order of script execution in Drupal.

(function ($, Drupal, drupalSettings) {
  Drupal.behaviors.customTelephone = {
    attach: function (context, settings) {
      // Define custom options for International Telephone Input.
      Drupal.webform = Drupal.webform || {};
      Drupal.webform.intlTelInput = Drupal.webform.intlTelInput || {};
      Drupal.webform.intlTelInput.options = {
        autoPlaceholder: "off"
      };
      console.log("Custom options set:", Drupal.webform.intlTelInput.options);

      // Initialize the plugin with extended options.
      $('input[type="tel"]', context).once('intlTelInput').each(function () {
        var options = {
          // Default options here
        };

        // Extend default options with custom options.
        options = $.extend(options, Drupal.webform.intlTelInput.options);
        console.log("Final options:", options);

        // Initialize the plugin with the final options.
        $(this).intlTelInput(options);
      });
    }
  };
})(jQuery, Drupal, drupalSettings);

custom_telephone:
  version: 1.x
  js:
    js/custom_telephone.js: { }
  dependencies:
    - core/jquery
    - core/drupal
    - core/drupalSettings
    - webform/webform.element.telephone

Can you please any timeline to covered this module under Drupal's security advisory policy. As I really need this module to use in PROD Env.

If you can tell me any date so it would be helpful for me.

Thanks

Mubasshir Khan → created an issue.

Mubasshir Khan → created an issue.