5 posts in this topic
Recently Browsing 0 members
No registered users viewing this page.
Hi, I'm new to PW. I could not find anything about this in the form or the documentation.
I installed PW 3.0.54 with the new regular profile using markup regions. Now there are already some pages and blog entries there. Can I install multilanguage on an existing page that had no translation previously? Would seem that this should be possible. But it seems like all pages act as languages now:
I compared my installation with a site-multilanguage installation and found there is a template called "language" – this was missing in my site-regular profile so I exported and importet that template. Now I git the following error upon import
language.fieldgroupFields: Unable to find field: language_files
and after completing import I get a breaking error:
Error: Uncaught Error: Call to a member function setIsDefaultLanguage() on boolean in /home/ubuntu/workspace/pw3/wire/modules/LanguageSupport/LanguageSupport.module:170
You can see it here:
user > thanks4help
I'm now kind of lost on how to do it propperly… Basically: Does anyone know how to add languages to an existing single-language website? Thanks for your help
I've just had this wonderful idea : I know that multi-language field (example : $page->myfield) are useful whatever the page. I mean you can define a multi-language field in your homepage and make use of that same field in another page and benefit of the different translations there too.
Is it the same for translatable string (such as echo __("blablabla")) ? Am I able to translate some strings in one template and benefit of those translated strings in another template ?
I'm using translatable strings such as :
echo __("Hello"); It works on my dev configuration but when I upload the website on the production environment, it only displays the default language.
Do I have to upload some special files where could be located the translations ?
Recently I launched a module -ImportPagesPrestashop-, and now I was thinking if it is worthy to translate this module in several languages (starting with a translation in dutch, because I'm from the Netherlands). Is it worth to put the effort into the translation or do you guys think ->English is the best and translations are not needed?
Thanks in advance,
My project is a multilanguage one.
On the homepage, I have a header menu where I display link of features, example :
<?php $lg = $session->lg; echo $page->localHttpUrl("$lg").'dashboard'?> ?> My website displays french by default.
The homepage is : www.website.com/ (in french default language)
The link in the code above is rendered as : www.website.com/dashboard
When I click on this link, it does a 301 -> www.website.com/fr/dashboard
dashboard is a child page of the homepage.
When I does the same in a non default language, such as 'en' / english for example, it doesn't do that 301 because the generated link in my code is www.website.com/en/dashboard
I know there is an option in the core module LanguageSupportPageName to prefix the page of the default language by 'fr' (in my case), but apparently it's not recommended.
"Choose Yes if you want the homepage of your default language to be served by the root URL / (recommended). Choose No if you want your root URL to perform a redirect to /name/ (where /name/ is the default language name of your homepage)."
Maybe it's not recommended because it's causing a 301 when you arrive the first time on the homepage (from / to /fr).
So how I could generate my link in the menu such as it displays www.website.com/fr ? I can do it by hacking some php of course, but perhaps there is a PW way to do it ?