🇮🇳India @kalpanajaiswal

Updated the MR with minimum Drupal compatible version to support attribute discovery.
Please review.

Thank you!

MR has been raised and ready for review.

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

Created an MR, ready for review.

kalpanajaiswal → changed the visibility of the branch 3453922-sort-the-option to active.

README.md file has been created and ready for review.

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

kalpanajaiswal → changed the visibility of the branch 3453922-sort to hidden.

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

Raised the MR with condition.

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

Rerolled the patch for contrib module only.

MR https://git.drupalcode.org/project/drupal/-/merge_requests/8325 has been updated against 11.x

As per the suggestion .gitlab-ci.yml is removed from the commit.

Both Patch and MR have been created to address the issue.

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

kalpanajaiswal → changed the visibility of the branch 3454448-add-btn-block-config to active.

Hi Diwakar,
I have updated the Readme file as per the standards.

MR created to sort the $handlers_options in EntityReferenceItem::fieldSettingsForm().

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

I've been working on replicating this locally, and I believe it's functioning as expected after addressing other issues in the queue.
After looking into the issue " https://www.drupal.org/project/search_api_autocomplete/issues/3024266 ✨ Avoid multiple results for the same keyword Needs work "
The goal is to eliminate duplicate suggestions.

The specific question I have is regarding keywords that appear in both lowercase and uppercase.
For example, if we have "Backup" and "BACKUP," should the suggestions include both "backup" and "BACKUP," or just "backup"?
This needs to be aligned with the fix for issue 3024266.

I couldn't find a specific option to enable case-sensitive suggestions. However, if we want the suggestions to be case-sensitive, then the results should also be case-sensitive.

MR https://git.drupalcode.org/project/drupal/-/merge_requests/8398 created for the issue.

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

The issue is not reproducible.
I have tested the feature with Drupal 10.2.7 & search_api_autocompleteVersion: 8.x-1.8 version.
Adding few screenshots for help.

I tried to replicate the issue but it didn't reproduce.
Drupal version: 10.2.7
office_hours module version: 1.17.0

Adding few screenshots after testing in my local setup.

MR has been created and covering all the points mentioned in remaining tasks.

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

MR created to replace readme.txt file to readme.md file.

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

MR created to replace readme.txt file to readme.md file.

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

Created a MR
MR: https://git.drupalcode.org/project/drupal/-/merge_requests/8325

  /**
   * The fields on which to sort.
   *
   * @var array
   */
  protected $fields;

  /**
   * Constructs a new Sort object.
   *
   * Takes an array of sort fields. Example:
   *   [
   *     [
   *       'path' => 'changed',
   *       'direction' => 'DESC',
   *     ],
   *     [
   *       'path' => 'title',
   *       'direction' => 'ASC',
   *       'langcode' => 'en-US',
   *     ],
   *   ]
   *
   * @param array $fields
   *   The entity query sort fields.
   */
  public function __construct(array $fields) {
    $this->fields = $fields;
  }

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

First param comment updated as per the parent class

If you have an entity with a moderation state and want to run the scheduler on entity based on a moderation state.
It will not support.
For example add an article with a scheduler on to be published in future.
But if someone made any changes and moderation state updated in draft mode, it shouldn’t be published.

Here is the thing.
If you look in to the file "inline_entity_form/src/Plugin/Field/FieldWidget/InlineEntityFormComplex.php"
Inside function "formElement"
A piece of code written to call the theme hook for each referenced entity.

$element['entities'] = [
      '#tree' => TRUE,
      '#theme' => 'inline_entity_form_entity_table',
      '#entity_type' => $target_type,
];

For example if we have 1000 reference entity, this theme hook be called 1000 times and due to this process is gets slow.

Just remove the '#theme' attribute and test the functionality.
UI will be broken as theme is not there but process will me much faster.

We faced the same issue and remove the '#theme' and handled broken UI separately

I am adding a screenshot for help.
I have just run a test with 25 reference entity, so there is nut much difference in loading time, but if you test this with more entity reference content like 200 or 300, you will see a huge difference.

Create an MR with patch #11
MR: https://git.drupalcode.org/project/drupal/-/merge_requests/8311

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

Merge request created to add the comment on construct object.
MR: https://www.drupal.org/project/drupal/issues/3450567 🐛 GenerateTheme::__construct() does not document its parameters Active

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

A patch has been created to solve the issue.

kalpanajaiswal → changed the visibility of the branch 3103334- to hidden.

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

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

Created a MR for Drupal 11.
MR: https://git.drupalcode.org/project/drupal/-/merge_requests/8299
Branch: 2951487-check-instance-type

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

Created a MR from patch #6
MR: https://git.drupalcode.org/project/drupal/-/merge_requests/8297
Branch: 3353388-type-error-implode

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

Created one MR from patch 2.
Branch: 3424320-invalidargumentexception-issue

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

I tried all the above mentioned steps and below are the response.

When I visit "/fr/admin/content'
One popup came, I selected english

I refreshed the page and now I selected french

I tried to change "Содержимое" to another the word.
Value is getting updated on "/admin/structure/types/manage/page/fields/node.page.body" page.
Even success message it printing right value.
But its not visible on other pages like "/admin/structure/types/manage/page/form-display",
"/admin/structure/types/manage/page/display",
"/node/add/page".

Its still showing the old value instead of new.
Looks like issue now.

I replicated the same behavior in Drupal 9.5.11 as well.

The issue is not reproducible in Drupal 10.2.6
Feature is working as expected, adding few screenshots for help.

The issue is not reproducible in 10.2.6.
Functionality is working as expected adding screenshots for help.

Converted Editor plugin discovery to attributes.

Converted Editor plugin discovery to attributes.

Remove library, drupal settings and other attachments from response.

Updated incorrect error-message class for the details and detail vertical tabs components.

Updated incorrect error-message class for the details and detail vertical tabs components.

Unwanted code has been removed based on the last comment.

I followed this doc https://relay.so/docs/1.x/installation#using-docker for installation but getting this error
"PHP message: Error: Class "Relay\Relay" not found in /var/www/html/docroot/modules/contrib/redis/src/Client/Relay.php on line 14 #0 /var/www/html/docroot/modules/contrib/redis/src/ClientFactory.php(186): Drupal\redis\Client\Relay->getClient('redis', 6379, NULL, NULL, Array, false)