The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.In #3338988: Completeness of l10n_community, we figured it is impossible to highlight a project in 3.0.x. We need to port this missing part.
Resources:
- Screen comparison between Drupal 7 and Drupal 11.
- how to install locally the Drupal 7 version of Localize.
| Comment | File | Size | Author |
|---|
Issue fork l10n_server-3564295
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #4
dydave commentedOK, after looking at the code it appears the highlighted project feature has already been implemented in:
https://git.drupalcode.org/project/l10n_server/-/blob/3.0.x/l10n_communi...
So basically, the module currently uses a Controller class to display the section about the highlighted project, see in particular methods
titleandbuild(search forhighlighted_project).By default, the highlighted project is Drupal Core and this feature can be tested at anytime at:
Either the front page: https://localizedrupalorg.ddev.site/
Or https://localizedrupalorg.ddev.site/translate which is currently set to redirect to the front page (configured in the basic site settings).
Therefore, we assumed the real issue here was the ability to control the project currently highlighted in the corresponding section and page.
So we added a back-end configuration form accessible at:
/admin/config/l10n-community/settings, which should allow changing the highlighted project.See the result locally with the Admin Toolbar module being highlighted:
Moving issue to Needs review as an attempt to get more testing feedback and reviews.
Feel free to let us know if you encounter any issues while testing or would have any questions or concerns on any of the suggested changes, we would surely be glad to reply as soon as possible.
Thanks in advance!
Comment #7
fmb commentedThank you!