🇪🇸Spain @pcambra

Merged, thanks

Well there's no conflicts because there are no changes now.

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

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

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

Needs rebase

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

I think this is still happening on 2.x

Finally had time to look at this and I think it's fixed, adding it to 2.x and 3.x

Finally had time to look at this and I think it's fixed, adding it to 2.x and 3.x

pcambra → created an issue.

Done :)

Moving this to a 2.x branch! thanks Mike

pcambra → created an issue.

I understand what you're explaining. What's missing is an upgrade path as mentioned earlier.

I will add a 3.x branch for the DER changes :)

This is definitely missing a migration, we can't just do this.

I still see that this overlaps with ✨ Allow Like Entity to support multiple entity types Active , I feel we should be do one or the other but not both. I am not opposed of adding a dynamic ER dependency.
This probably justifies opening a 3.x branch, but we still need an upgrade path.

Thanks for the pointer, this makes sense.

pcambra → created an issue.

pcambra → created an issue.

pcambra → created an issue.

What's going on is that the tabs are picked from the latest translation revision from ERR so if you have a site in English and Spanish, whatever you save last, will win, adding a MR shortly.

I'm going to close this one with the changes suggested by the bot only, please add follow up issues if there are any other changes you'd like to make.

pcambra → created an issue.

Let's make this simpler and do just the icon, if someone wants the text, we can open another task.

You normally don't put your own patches as RTBC.

I've rebased this to be against 2.x

Thanks.

Please remove anything that is not D11 related and open separate issues for that.

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

Awesome, thanks!!

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

Awesome, thanks both!

Thanks all!

Example on how we could apply this:

on the .module file:

/**
 * Implements hook_field_info_alter().)
 */
function my_module_field_info_alter(&$info) {
  if (isset($info['block_field'])) {
    // Override the list class for the block_field field type to avoid comparing
    // plugin changes between revisions.
    // @see \Drupal\Core\Field\FieldItemList::hasAffectingChanges()
    // @see https://www.drupal.org/project/block_field/issues/3517759
    $info['block_field']['list_class'] = '\Drupal\my_module\BlockFieldItemList';
  }
}

The custom BlockFieldItemList class:

<?php

namespace Drupal\my_module;

use Drupal\Core\Field\FieldItemList;
use Drupal\Core\Field\FieldItemListInterface;

/**
 * Avoids block plugin fields to be compared between revisions.
 */
class BlockFieldItemList extends FieldItemList {

  /**
   * {@inheritdoc}
   */
  public function hasAffectingChanges(FieldItemListInterface $original_items, $langcode) {
    // If there are different items, then it is a change.
    if (count($this) != count($original_items)) {
      return TRUE;
    }

    foreach ($this as $delta => $item) {
      if ($item->getProperties()['plugin_id']->getValue() != $original_items[$delta]->getProperties()['plugin_id']->getValue()) {
        return TRUE;
      }
    }

    return FALSE;
  }

}

pcambra → created an issue.

pcambra → created an issue.

@macsim, oh dear, apologies for that, I didn't noticed that the default option didn't include you, should be fixed now!, thanks for letting me know!

I think this was included in 📌 Drush 13 compatibility Active , thanks!

Could you please confirm if this has been solved in branch 3.x?

Is this something that happens on 3.x branch as well?

Thanks all!!!

Let's merge this and fix whatever is missing afterwards, thanks all for the hard work on this one.

Well,. looking at the compatibility table in https://www.drush.org/13.x/install/#drupal-compatibility we cannot have a 3.x release that supports Drupal 10 and 11 AND Drush 11, so I'd be OK dropping it for 3.x

Should this be needs review?

I would suggest the 2.x branch is removed from the project page then, as it might be expected that users see a D11 version and they read only that.

Just changed the branch to be 3.x

Is this a duplicate of 📌 Support latest versions of drush for drush.services.yml Active ?

This has been/will be fixed by 📌 Support last delimiter to allow comma separated plus and Active and 🐛 str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in Drupal\Component\Utility\Xss::filter() RTBC , thanks

Merged into 2.x, thanks all!

1.x Branch is no longer supported

pcambra → created an issue.

Added langcode to the query and reference to the Drupal issue

I just found this issue myself, I think it doesn't really matter to group by uid, but we definitely need to group by language.

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

I think this is part of 📌 Automated Drupal 11 compatibility fixes for entity_reference_validators Needs review