Make Profiles Translatable

Any updates on merging?

After using this patch, I believe that it breaks some handlers of the view (/config/install/views.view.profiles.yml)
The patch make some changes on
-base_table: profile
+base_table: profile_field_data

I had to make similar updates on other lines (on sorts and arguments) that still mentionned the previous table.
These lines were sets on fields that also are on the profile table but it was still generate broken handlers.

It fixed the broken handlers.

While this patch worked on a couple of sites for me quite nicely, I was hit by an issue after updating from a distribution update. Turns out, that distro came with new and updated views, and those referred to the old/original table for views base tables, filters, fields, sorts and references.

Updating all views entities with a regex like /table: profile$/table: profile_field_data/g seems to have fixed it for me, once I imported those updated views entities.

That said, there should be 2 enhancements, I guess:

• Enhance profile_post_update_profile_views to not only update the base table but also all other table usages
• Find a way to re-run this hook when views get added or updated by module updates

any updates?

Will this issue be resolved?
Isn't this one of the remaining initiatives for multilingualization from Drupal 7 to 8?

I am grateful to all the developers.

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

The patch #54 indeed breaks profile views, however for the time being they can be fixed manually.

The actual issue we faced is that when a user account is translated and profile form is displayed on it, profile is not getting translated.

I created a pull request baed on #54 and made profiles widget match the root form language.

@alex.bukach can we test your commit? if so, can you change the status of the issue as "Needs review"?