Closed (fixed)
Project:
Localization server
Version:
3.0.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Nov 2024 at 16:43 UTC
Updated:
10 Apr 2026 at 22:16 UTC
Jump to comment: Most recent
Comments
Comment #2
_m commentedComment #3
fmb commentedComment #4
_m commentedI've made progress on the first and third item. However, the "Profile on primary site" link is something that feels like it is configured only on the production site (i.e. not custom code).
I will submit my contribution asap. I still need to format it as requested.
Comment #5
fmb commented@_m how is it going?
Comment #6
dydave commentedOK, I've started checking the project's documentation and will take a closer look at this issue.
Thanks for all the info @fmb!
Comment #7
fmb commentedInterestingly enough, this is not related to SSO. We can just retrieve the user ID on drupal.org that way with a GET query on https://www.drupal.org/jsonapi/user/user?filter[name]=USERNAME, and then extract the
drupal_internal__uidattribute (USERNAME can be "dydave" or "fmb" for instance). We would then be able to build this kind of URLs: https://www.drupal.org/user/619092.Comment #9
dydave commentedOK Felip (@fmb), I've pushed all the changes discussed together for this issue, in particular for the two requirements:
1 - list of translation teams (formerly "group audience"),
3 - Localization contributions: number of approved translations for each translation team.
The merge request: https://git.drupalcode.org/project/l10n_server/-/merge_requests/112
needs to be merged first and add a Views relationship plugin which is used in the other merge request:
https://gitlab.com/drupal-infrastructure/sites/localize/-/merge_requests/53
Which also contains multiple other changes: Upgrade of the code base, installation of additional modules, uninstalled unused modules, etc...
If possible, it would be great if these changes could be merged first, before fixing the second requirement with:
2 - profile on primary site (might be related to #3274544: Review integration of l10n_drupal_rest with drupalorg_crosssite),
We've started working on this last point, with a colleague, as mentioned by email, but it's most likely going to take a little bit more time...
Could probably land next week.
Let me know if you spot anything when testing the merge request, I would surely be glad to make additional changes.
Thanks in advance!
Comment #12
fmb commentedThank you so much @dydave for these nice and well-documented MRs! All tested and merged. Now, could you please add the new view in l10n_community/config/install (or l10n_community/config/optional, whichever is the relevant option here)?
Comment #14
dydave commentedSorry for the delay on this once again Felip (@fmb), but we took a bit more time to do a bit more testing and code clean-up before being able to push these changes.
The comments raised at #12 have been addressed in MR !117, with the missing views added, plus the last requirement for this ticket, with the User primary profile link block.
These changes should be merged before merging the changes containing the configuration changes to display the block from merge request:
https://gitlab.com/drupal-infrastructure/sites/localize/-/merge_requests/57
A few small additional changes were added:
Added PHPMyAdmin ddev plugin for local development purpose, since the project is using MariaDB anyway.
We noticed a block was wrongly displayed on the project releases page, so we updated the visibility settings of the language progress block, thanks to the contrib module
block_exclude_pages.At this stage, the user profile page should have all the features it currently has on the D7 site.
We would greatly appreciate if you could please try testing and reviewing this new round of changes and let us know if you spot anything else.
Feel free to let us know if you have any questions, comments or suggestions on any aspects of these merge requests or this ticket in general, we would surely try answering as soon as possible.
Thanks in advance!
Comment #19
fmb commentedThank you!
Comment #21
dydave commentedThank you everyone for the great help on this issue! 🙏
Glad we could get this one landed 😊