Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Title tells everything: please make the privatemsg tags translatable (provided by the privatemsg_filter submodule). It could be done with (an optional dependency on) i18nstrings.module, like other modules do.
Comment | File | Size | Author |
---|---|---|---|
#1 | privatemsg-1071470-1.patch | 3.91 KB | Boobaa |
Comments
Comment #1
BoobaaAttached is a patch against 1.3 that adds preliminary support for translatable tags. After applying it, one will be able to translate the tags. Anyway, there are still quite a bunch of things to do:
- display the translated tags (now only the original tags are displayed),
- make it possible to filter on translated tags (now the filter uses the tag name in the URL, which makes filtering on translated tags impossible),
- etc.
Comment #2
BerdirNot exactly sure why they need to be translated, tags are something personal and aren't shared across multiple users.
Why not simply save it as $tag_id? At least it shouldn't be inside values imho.
Powered by Dreditor.
Comment #3
BoobaaBecause the original string needs to be updated when it's edited, and this use case is handled by this very same code, too. (The original code without the patch handled it this way, too.)
Comment #4
oadaeh CreditAttribution: oadaeh as a volunteer commentedThis issue is being closed because it is against a branch for a version of Drupal that is no longer supported.
If you feel that this issue is still valid, feel free to re-open and update it (and any possible patch) to work with the 7.x-1.x branch (bug fixes only) or the 7.x-2.x branch.
Thank you.