Multilingual Support

This issue still valid in term of adding the language filter.
I fixed in 3.x-dev the issue with saving the language dependent data to views_url_alias, but the filter or view query still need to added to make sure we can filter by specific/current language.

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

The latest code wasn't selecting the correct entity translation.
It always picked the entity translation in the current user's language because the entity was resolved with the router service.
This issue can be reproduced by running a Pathauto bulk regenerate for all aliases on a multilingual entity.

I refactored the views_url_alias_get_path_entity_type function to ensure it handles entity translations properly when applicable.

However, I had to remove the views_url_alias_pathauto_alias_alter hook function. The comment in the hook says it’s for saving aliases during bulk updates

function views_url_alias_pathauto_alias_alter(&$alias, array &$context) {
  // Save alias during bulk update.

, but I don’t see how that’s the relevant place to save the data. Is it a workaround for something?

After I had installed this module on Drupal 10.2.3, I added a relationship in the views for 'URL alias', the related views page is broken. It is not working correctly on a multilingual website.