Search the Community
Showing results for tags 'multilanguage'.
-
Hi folks! I have a little problem with some language-alternate filefields file and file_en inside a repeaterfield. Some repeaters only contain geman files, others only contain english files. Looking at the german version, everything is fine, you see only german files. But looking at the english version, you see both english and german files because the default value is displayed if file_en is empty. Is there a way to not display the default value if file_en is empty? Regards, Falk
-
Hello guys, I'm new in the PW community and seems like i have a small problem.. I would like to know how can i reach to this page to activate the newly added language.... Thank you for your help....
-
i did a multilanguage-install. english and german are needed i set german as default (install german languagepack at default) then add english (en) as second language my date-output is custom: %A %d %B %Y (Details Tab) echo $page->date the problem is that i always get the english ouput.
-
Hello for all, I need to create multilanguage website for non-profit organisation. "Problem" is that ratio between number of pages for default and additional language is about 10:1 because additional content is only for representation (summary of organisation activities with max. frequency of administration 1 per month). Currently there is only 1 additional language (default + english), and probably there would not be any changes in the future. Only what I want is to get much as possible cleaner administration user interface becuse of relatively complex content structure (deep categorisation, featured content, document management, front permissions, related content, events, galleries, archive, tags...). One idea is to avoid standard PW multilanguage concept and use "category" for additional language (understand that in that case need to use "hard coded" queries). Another option can be multiple PW installation but I don't like that because of shared files (images, pdf files), and common content blocks/widgets (galleries...). Additional language content (almost in >75%) is not in direct relation with default language content (like multisite variant, but with common templates, images, documents, media files etc.). Please, what is your suggestion about that website structure organisation? Thanks, Sasa
-
Hi everyone, I want to use the core module PagePathHistory in a Processwire instance with multi-language URLs/page names activated through the core module LanguageSupportPageNames. From looking at that old Post by Ryan I was pretty sure that it should work without any problems and was surprised that actually it doesn't. PagePathHistory only saves entries to it's DB table when the page name in the main language changes, not when any of the other language names change. Looking at the code this is no suprise as PagePathHistory only hooks Pages::moved(), Pages::renamed() and Pages::deleted(), none of which would be triggered by a change in a language page name. Starry-eyed I started to implement the missing language-awareness in the module, how hard can it be, eh? ...pretty quickly it turned out that this isn't that simple, so I decided to first ask for some help and guidance. Does anyone maybe already work out a solution for this particular problem or something similiar? The problem with the implementation is that after saving a page with changes to language names, there still has to be a means of accessing the old names. For the default language name this is pretty simple because it's saved as $page->namePrevious. For language names the module would have to deposit the original names for later to build the PagePathHistory-URLs. I've been looking through all hookable functions in core classes/modules but haven't found the best place to hook into to implement this functionality. Does anyone have an idea where this would be done best? Any help is appreciated. Thanks a lot in advance Marc
-
Hello guys, hope you all have a great day. so I want to translate my templates element based on selected languages i.e "read more" button, "follow me" button, etc. in wordpress we can do something like this <?php _e( 'Some text to translate and display.', 'textdomain' ); ?> and then translate it via .mo files, how to achieve similar to this using PW or is there better way doing this?
-
Hello @ all, I am new to Processwire and I am struggling for a while with this problem. I have setted up a multilingual site with a language switcher. The switcher works fine except on the homepage. It seems the aliases for the different languages (German: startseite, English: home) will not be taken on the homepage. If I switch to the other language on the homepage it doesnt work - it wil be always in German. The aliases will not be added to the homepage url so it is always the root url and this maybe causes the problem. I found this in the explanation: Please note that the URL for the default-language homepage is always your site's root URL, regardless of what you specify in the homepage name. This is intentional, as it's not desirable to have a homepage that produces a 404 or immediately performs a redirect to another URL. If populated, your homepage name for the default language is still applicable for the rest of the pages in your site. But how can I switch on the homepage to another language??? Do I need the language prepend in the urls (de, en,...)? I have searched in the forum but I couldnt find a solution to this problem. I use the latest version of Processwire. Can anyone point me into the right direction? Best regards Jürgen
-
If I have a field for URL, say a page needs to link to another page. If the user is viewing the site in Spanish and that link points to the English version, does it know to output the spanish version of the link? And if so redirect the user to the spanish URL? Is the language the visitor views the site in, kept in sessions or something for it to do this? I'd rather not have 2 URL fields
-
I have tried to change the title fieldtype from Title to TitleLanguage in PW 2.4 got Error: Exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_title.data1019' in 'field list' (in /wire/core/DatabaseQuery.php line 86)
-
Hi there, I was wondering, how I could access the additional data stored to the $page->body when using additional / multi languages. Usually you use $page->body to echo the data to the page. Now I got that additional datafield "data1031" where the alternative language is saved in but I can't figure out how I can echo this particular string on the the page. Maybe someone of you clever folks can help me. Best regards
-
When I get in contact with processwire after a recommendation of a friend the first step after installing was a look in the database. Why? I had bad experiences with a shop-system I used, which ended up in digging and modification of the source code to make it work properly. Finally the biggest problem was the database with its questionable structure and data redundancy. I said goodbye to the shop-system after. With processwire I felt immediately in love because of its super slim and clear structured database without redundance of course from which results a lot of opportunities to grow. But since I use multilanguage support in processwire it makes me a little gripes when I see the way of Language Implementation in the database. About the conventional structure as an example: users are stored in pages and passwords are stored fields 'field_pass' which refers to the page (perfect) Structural changes since multilanguage support: pages and fields either have data (information about language) stored in column titles like 'name1007' or 'data1007' (not really perfect) What happened while making processwire multilingual? The tablefield in the database 'name' in table 'pages' wasn't unique anymore. 'name' from now on would have to be a field 'field_name' like 'field_titel' with its own databasetable. Same to status. The status of a page should be stored in 'field_status'. Possible solution: There exists already a field 'field_language' which stores the language of the page 'user'. This field could store easily the language of every page. Every page in every language should have its own database entry and unique id, even the rootpage with parent_id '0' should have this. All name and status columns should be outsourced to fields. Language relevant columns like 'data1007' in fields are obsolete. As a result every field becomes multilingual automatically, because it references to a unique site. I know that many people Ryan first of all have spent a lot of time and work to make this great system available. And I have a lot of respect before this people. I am happy to use processwire and I love it. But since I run in problems when I decided to switch an alternative language to the default language burrowing around in the database I started to think about some facts. I am pretty sure processwire will run in problems following the pursued way. On the way making processwire to the worlds best CMS the database as the heart of the system should be young, healthy and proper.
-
Hi all, I just switched to processwire from MODx and I am really impressed of how clean, fast and intuitive this system is. My first project with processwire happens to be a multi language site, and I am really happy that it can be done with a single page tree. However, I had to dig the forums a lot to find all information i needed to get everything working, so I thought I share my newly gained knowledge... The order of the steps is important, especially if you are working on IIS (which can inflict database damage if you add languages before you change the field types!) 1. Install the Language support modules: - Languages Support - Languages Support - Fields - Languages Support - Page Names 2. Change any existing Fields of types Textfield/Textarea/PageTitle to TextLanguage/TextareaLanguage/PageTitleLanguage You now will have an input field for each language you add. 3. Set up your languages under Setup->Languages (define a name and title for each language. For each new language, you will have to add a title to all the other languages in that new language) 4. Edit your homepage, set it to hidden and unpublished. UPDATE: don't set the homepage to unpublished, the first-child-redirect won't work! (I realized just now, because if you are logged in as admin, it does work) For each language, you have to define a unique name (e.g. "de" and "en") 5. Edit your "home" template to redirect to its first child: <?php $session->redirect($page->children->first()->url); UPDATE: this is not essential... as ryan pointed out, it might even be better not to do it (for SEO-optimization) 6. If you have something like $children->prepend($homepage); in the menu part of your head.inc, remove it (you don't want the home page to show up in your menu) UPDATE: if you left out the redirect option, you'll want to leave this out as well. 7. To switch languages, add this snippet to your head.inc: <ul> <?php $user_lang = $user->language; foreach($languages as $language) { $user->language = $language; if($language->name != $user_lang->name) { echo '<li><a href="'.$page->url.'">'.$language->title.'</a></li> '; } } $user->language = $user_lang; ?> </ul> Each language except the currently active one will be displayed in a list (of course, this can also be done with a select field). UPDATE: Ryan pointed me to a better solution for the langugae switch: http://processwire.c...s-urls/?p=33537 8. Done. Now your page urls should look something like path/to/root/en/my-page, or path/to/root/de/meine-seite It took me less than a day to set up processwire, install my html template and configure the site to be multi-language... this is so great, considering the pain multilanguage sites usually cause with all the other CMSs... Keep it up! UPDATE: I was a bit quick to post a tutorial just after one day working with PW... should have made some more research beforehand. Just got a little too excited there... I'm still impressed by the system and plan on digging deeper into it.
