Closed (works as designed)
Project:
Filebrowser
Version:
8.x-2.x-dev
Component:
Directory Listing Pages
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2019 at 12:09 UTC
Updated:
5 Dec 2019 at 17:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
clivesj commentedOn my system the Filebrowser strings appear as expected.
Please note the following:
Drupal has to discover the string before it can added to the translation.
For this you have to:
- Visit the page where the string is.
- Do this *in the target language* .
- Run cron.
Please let me know if this solve your issue.
Comment #3
clivesj commentedI am closing this one. Please reopen if needed
Comment #4
gpappc commentedHi and thanks for your reply. What do you mean by saying "Do this *in the target language*"? About the point where I am now... Under /admin/config/regional/translate now Drupal finds the strings and I am providing a translation, but in the frontend is still in English. I have uploaded two pictures to see.
Comment #5
clivesj commentedLets say your site is installed in English and you want to translate it in Dutch.
You have to go to the page where the original translatiin is. Otherwise Drupal does not discover the string to be translated. But be sure that you visit the page in the target language, in Dutch. The string will be displayed untranslated but now it is disvovered by Drupal and you can find it in the interface.
There are may ways to force Drupal in the target language, depending on the language selection methos you configured
Comment #6
gpappc commentedI have visited the page but still Drupal doesn't recognize them. I have created many strings with t() in my module and then Drupal after one visit was able recognize them. I don't know what's happening :/
Comment #7
clivesj commentedThere are reports that sometimes you have to visit a page multiple times and that you have to also clear cache a couple of times. I am afraid this is a Drupal thing.