Hi Alexei, The answers are yes to all your questions : - Yes it is working correctly when using the 'en-US' language code (I tested removing the 'en' translated folder and in this case it takes a default english, if I add the 'en' translation folder with spanish or french translations in it, everything is working the same and displaying the translations). - When chosing another language code with its associated translation folder, the search page is starting to load but the errors I sent last time appears. I do not understand why in this configuration, the scripts are not found. I also tried to move them but the result is the same. I wondered if I did correctly all the steps but it is working with the 'en' (and not a default folder), therefore I am really stuck too. - Yes I cut the screenshot but nothing is missing.
Thanks for your time. I am going to investigate a litle bit more. I think I can fix one language per project, thus I can bypass the problem putting all my translations in the 'en' folder. I let you know if I find something new. Cheers, Marlene Le mercredi 12 juin 2019 20:24:47 UTC+2, Alexei Peters a écrit : > > Hi Marlene, > I'm really stuck as to what is going on here. Just to confirm, the search > page loads and runs correctly (you can search for resources without issue) > when using the 'en-US' language code? > For some reason it looks like the 2 scripts that the base page requires > (via require.js) aren't loading properly, but I'm unsure why it seems to > work with the 'en-US' language code. I wouldn't think that would have any > affect on how the base page loads at all. > The screen shot you sent seems to be truncated. Is that all that there > was when loading the page? > Cheers, > Alexei > > Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 > > > On Tue, Jun 11, 2019 at 12:54 AM Marlene Gilles <[email protected] > <javascript:>> wrote: > >> Hi Alexei and Alina, >> >> I did not found a solution yet, other than entering the translations >> inside the en/LC_MESSAGES/django.po file. >> I enclose the errors I obtained (search page is loading when choosing >> en-US language_code despite the error message on /media/img/Workflow.png). >> >> Cheers, >> Marlène >> >> Le lundi 10 juin 2019 19:50:02 UTC+2, Alexei Peters a écrit : >>> >>> Hi Marlene, >>> Can you post a copy of any errors you're seeing, either directly from >>> the search page, or from the console. >>> Cheers, >>> Alexei >>> >>> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 >>> >>> >>> On Wed, Jun 5, 2019 at 6:18 AM Marlene Gilles <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> I would like to change the language of the application (v4.4.1) by >>>> first setting it manually (without using LocaleMiddleware even if it is my >>>> ultimate goal). >>>> >>>> I have modified the settings_local.py file: >>>> LANGUAGE_CODE='fr-FR''. >>>> LOCALE_PATH=('path_to_my_locale_folder',) >>>> >>>> I created the "locale" folder and I ran: >>>> django-admin.py makemessages ... >>>> I added the translations and then run: >>>> django-admin.py compilemessages >>>> >>>> I can see the change on the home page but when I click on the >>>> equivalent of "search", the page fails to load. This only works when I >>>> select the language in-** (with translation or not add in >>>> en/LC_MESSAGES/django.po). Even a copy and paste of the folder by just >>>> changing its name to fr instead of en is not working. I need an access to >>>> several languages therefore I cannot add my translation directely in the >>>> en/LC_MESSAGES/django.po file. >>>> I obtain an error saying that /nifty.js and /views/search.js are not >>>> found. >>>> >>>> I probably forgot a step, can someone enlighten me? I found an old post >>>> from 2016 but I'm not sure it's up to date and the documentation is no >>>> longer accessible. >>>> >>>> Regards, >>>> Marlene >>>> >>>> -- >>>> -- To post, send email to [email protected]. To unsubscribe, >>>> send email to [email protected]. For more information, visit >>>> https://groups.google.com/d/forum/archesproject?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Arches Project" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/archesproject/6d197fec-9e56-4c7a-b77a-0821cfd8ad85%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/archesproject/6d197fec-9e56-4c7a-b77a-0821cfd8ad85%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> -- To post, send email to [email protected] <javascript:>. To >> unsubscribe, send email to [email protected] <javascript:>. For >> more information, visit >> https://groups.google.com/d/forum/archesproject?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Arches Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/archesproject/b7f84d43-1925-49c4-b9c8-9ba169ec7927%40googlegroups.com >> >> <https://groups.google.com/d/msgid/archesproject/b7f84d43-1925-49c4-b9c8-9ba169ec7927%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/archesproject/1b84fae9-81f3-454f-92df-b7b72eecd1fc%40googlegroups.com.
