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.
In the stream where user selects "Public - Visible to all visitors of the site" / "Community - Visible only to members who are logged in" options can not be translated.
Also while adding a node "Public - visible to everyone including people who are not logged in" and "Community - visible only to logged in members" are not translatable.
Can anyone suggest a quick fix? Maybe i am missing something.
Comment | File | Size | Author |
---|---|---|---|
#7 | add-schema-files-for-fields-2853954-7.patch | 2.21 KB | tarasich |
Comments
Comment #2
alpp CreditAttribution: alpp commentedAlso, social post strings like "posted" "commented on content in" "created an event" etc. in the stream, are translatable, but the translations do not take any effect?
Will Open Social have multilingual features? Or at least will it be translatable to another language?
Comment #3
alpp CreditAttribution: alpp commentedAfter updating all "message templates", now the new publishings are translated correctly in stream.
But i'm still unable to translate public/community dropdown texts.
Comment #4
maikelkoopman CreditAttribution: maikelkoopman as a volunteer and at Open Social for Open Social commentedValues of the dropdown are stored in the DB: /admin/structure/post/settings/fields/post.post.field_visibility/storage
Comment #5
alpp CreditAttribution: alpp commentedYes i saw it, but isn't there an easy way to make them translatable, for a multilingual site? Even when i translate them, the icons within options just disappear.
Comment #6
ronaldtebrake CreditAttribution: ronaldtebrake as a volunteer and for Open Social commentedComment #7
tarasichHi there! We needed to translate these fields for one of our projects.
So here is a patch with *.schema.yml files for two fields:
- entity_access_field
- dropdown
It will allow to translate them.
Comment #8
tarasichComment #9
andypostIt totally makes sense to have config schema defined
BTW it shows missing test coverage for config schema
Comment #10
ribelHere is PR from @tarasich: https://github.com/goalgorilla/open_social/pull/413
Comment #11
jochemvn CreditAttribution: jochemvn for Open Social commentedHi @andypost,
PR looks good. I'm only wondering what you mean with: "BTW it shows missing test coverage for config schema"
Jochem
Comment #12
jochemvn CreditAttribution: jochemvn for Open Social commentedHi,
I've merged the pull request. Will be part of the next release of Open Social.
Thanks for your contribution!
Jochem
Comment #13
jochemvn CreditAttribution: jochemvn for Open Social commentedComment #14
andypostI mean that there should be some test coverage to catch such errors