🇩🇪Germany @Schoenef

this patch removes the warning.

schoenef → created an issue.

#8 works fantastic! Thx @le72.

I feel this is kind of a missing feature of the moule.

This patch fixed it for me:

Adjusting core appears not be the solution here, I think the second call to

NestedArray::setValue($form_state->getStorage(), $parents, $imported_tablefield['rebuild']);

Should not use NestedArray but might need a custom implementation, as the storage can contain entities.

I did a bit of debugging and for the working /media/add form $triggering_element['#name'] is "tablefield-paste-field_data_values-0"

It entes in Tablefield.php line 403:

elseif (isset($triggering_element['#name']) && $triggering_element['#name'] == 'tablefield-paste-' . $id) {

For the media overlay (not working) $triggering_element['#name'] is "tablefield-paste-media-0-fields-field_data_values-0", it also enters line 403.

The issue occurs in the rebuild call, because media[0] is suddenly a MediaEntity, not an aray
0 = "media"
1 = {int} 0 <--- this returns an instance of Drupal\media\Entity\Media
2 = "fields"
3 = "field_data_values"
4 = {int} 0
5 = "tablefield"
6 = "rebuild"

It is of course not an array anymore.

Sugestion is to check for an entity and pull the fieldvalues into an array in this case.

schoenef → created an issue.

Linking up https://www.drupal.org/project/yoast_seo/issues/2867785 → , yould be great to have this properly translatable.

Potentially a duplicate of https://www.drupal.org/project/yoast_seo/issues/2867785 →

Appears to be a duplicate of https://www.drupal.org/project/yoast_seo/issues/2867785 →

Hi, is there any update on this one? It appears to be still not possible to translate the analysis results of the module.

Is there any clean solution for this? in the code, I can see

```
// TODO: Figure out the required i18n functions and link them to Drupal.
```

it would be great, if the analysis results could be translated.

Hi Guys, sorry I did not see this issue - I accepted the MR and created 2.1.3 for it.

Best wishes
Andreas

Probably better like this, in case the selective is not depending on a relationship.

This patch solves the issue.

schoenef → created an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Long done I think.

The project has a composer.json

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

Please open a new issue for the 2.0 version, if this is still an issue.

I applied teh patch, thx!

Please open a new issue for the 2.0 version, if this issue has still any relevance.

Please open a new issue for the 2.0 version, if this issue has still any relevance.

Done via https://www.drupal.org/project/views_xml_backend/issues/3369810 📌 Automated Drupal 10 compatibility fixes Needs review

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Please open a new issue for the 2.0 version, if this issue has any relevance still.

Alright, I'm now the new "bugs only" maintainer of this project and just released the version 2.0.0. Thx a lot @bspeare for doing the work on it - if you like I can make you a maintainer as well now.

The MR is merged and I'll clean out the old tickets now.

Please reopen this one, if it still does not work for D10.

Best wishes
Andreas

Hello dear Drupal.org Project Owbership Team,

I'm still interested in offering my help to maintain this project.

It would be great, if it could happen now.

Thx a lot!
Andreas

Thx a lot Alberto, see you in 14 days :)

dear Drupal.org project ownership team,

the current maintainers of this project appear all to have left, and they have not responded within 2 weeks. I contacted them multiple times via the drupal.org contact form. In order to keep the project usable, zany and myself would like to offer maintainership for this project.

The link to the project is this: https://www.drupal.org/project/views_xml_backend →

Thx a lot!
Andreas

Alright, will do. The `Open Ownership Pledge` Tag is not required? I've read somewhere, that it should be added.

Hi @avpaderno, you mean that we have to wait 2 more days before moving the issue? Or did we overlook some step in the process?

Thx a lot for a short feedback!
Andreas

Hello dear Drupal.org project ownership team,

the current maintainers of this project appear all to have left, and they have not responded within 2 weeks. I contacted them multiple times via the drupal.org contact form. In order to avoid further delays, I would like to raise my offer from co-maintain to maintain at the same time.

The link to the project is this: https://www.drupal.org/project/views_xml_backend →

If you can see, that the current maintainers have not logged in to drupal.org for a long time, I would appreaciate if you could start the process maybe now instead of waiting two more weeks?

Thx a lot!
Andreas

A yes, no answer whatsoever so far. I'll move this issue to the Drupal.org project ownership issue queue on friday.

I contacted again the whole team via the drupal contact form. @zany, if you are on facebook or twitter, maybe it is worth a shot there as well? Some of them have social links in their profile. Personally Im not on either and can not contact them there.

Alright, I found https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → and try to follow the procedure via https://www.drupal.org/project/views_xml_backend/issues/3478213 💬 Support in Maintenance Active - it wil take a month... fingers crossed, we can make it faster.

I contacted all current maintainers for accepting me as o-maintainer.

Hi @bspeare, I'm not sure if I can do it, but for you I think it would be possible to get co-ownership of this module following https://www.drupal.org/node/2938367#s-how-to-apply-for-ownership-or-co-m... →

I have the feeling, that the current maintainers are not really active anymore...

schoenef → created an issue.

The MR (thx a lot @zany) works well for us. In my opinion it can be merged and released.

Hi @bspeare, is there a way to include the whole MR as patch somehow? Then I can test it in our site.

Thx a lot!
Andreas

Hi guys, is there any news on a proper D10 release for thi smodule?

Thx a lot!
Andreas

Thank you! I had the feeling this was build somehow for something different then I thought. I'll try OIDC, it looks also good.

I don't need to connect to something using oauth, but if I had to, I would still not know how to actually use this module in a real world example. Maybe it would help to add a simple example to the documentation?

Best wishes and thx again for the clarification!
Andreas

schoenef → created an issue.

I stand corrected - it only works together with the path from #42 like I described above.

For me the patches do not work - but if I unse undefined as redirect language and don't select an actual node, but a lcoale path, it works

For example:

Path: docs/DOC-1763

To: /de/node/2

Redirects then to the correct DE url alias of the node/2

This is not a good design and totally not obvious, but I guess this could count as "work as designed".

I'd preffer a selection "Destination Language" thou, if more then one language is defined in the site.

I also had a closer look now, and it looks like this happens for multi language setups. In my case the taxonomy had as language "not applicable", so the permissions by term are stored with langcode zxx - BUT when being loaded, it takes the current language (en) - so it is not found.

extending the queries to pull also und and zxx languages might help, but I got a feeling that this would touch very much the core of this module and also potentially introduce bad side effects. However, it would be desirable to allow language independent access taxonomies for multi language sides.

I did test this in web/modules/contrib/permissions_by_term/src/Service/AccessStorage.php:

Before:

public function getRoleTermPermissionsByTid($term_id, $langcode) {
    return $this->database->select('permissions_by_term_role', 'pr')
      ->condition('tid', $term_id)
      ->condition('langcode', $langcode)
      ->fields('pr', ['rid'])
      ->execute()
      ->fetchCol();
  }

After (works as expected in the display, not tested further):

  public function getRoleTermPermissionsByTid($term_id, $langcode) {
    return $this->database->select('permissions_by_term_role', 'pr')
      ->condition('tid', $term_id)
      ->condition('langcode', [$langcode, 'und', 'zxx'], 'IN')
      ->fields('pr', ['rid'])
      ->execute()
      ->fetchCol();
  }

The language is all over, so this would definitely require thorough retesting and an architecture decision/evaluation of the main maintainers.

To make a long story short: Is there a way to support a language independent permission configuration in a multi language site?

Thx a lot!

Hi guys, I have the same problem with 3.1.33 and the patch also does not work for me. To me this is a pretty critical issue, as it kind of makes this version unusable.

Some feedback would be great!

This patch could be a way to achieve this by configuration (just for the email)

For me (having the patch of #3424946 installed) it does not throw errors at all. I actually would like to send a error message to the user, if the contact is already in the list.

So from the functional point of view, this works very well - I have just installed and tested it.

Codewise it is also fine from my point of view.

Thank you! I did not see the plain diff link.

It applies very well by adding

"patches": {
            "drupal/sendinblue_api": {
                "#3424946_doi": "https://git.drupalcode.org/project/sendinblue_api/-/merge_requests/2.diff"
            }
        },

to the composer.json file.