9

Have a look at transcribe. i am currently using it with structure and am pretty satisfied with it. The way you are proposing to do this will probably end up confusing visitors, as they will be seeing 2 languages mixed. With transcribe you will be creating different entries, and content of the site does not have to be equal. Each language will have it's own ...


6

I don't use Structure that much so here is the process and add-ons I use to develop multilingual sites in EE in case someone is looking for an alternative: Language Framework: I usually use Biber Multi Language Support for this although I will probably be trying Transcribe on my next project. In the case of Biber it will allow you to define your languages ...


5

Going to toot my own horn here. Publisher supports Structure and doesn't require any funky conditionals or nonsense in your templates to get the navigation to render. http://boldminded.com/add-ons/publisher


4

Taken directly from Structure's Docs: ( http://buildwithstructure.com/documentation/multi-language_sites/ ) The recommended method is to have your default language at the top level and make separate branches for your alternate languages like this: /about /services /contact /es/about /es/services /es/contact /fr/about /fr/services /fr/contact You can ...


4

Keyword searches with Low Search are diacritic insensitive. That is to say, both the collection index and given search terms go through an algorithm to strip them out or replace them with unaccented equivalents. LS uses EE's native $foreign_characters array for this, located in /system/expressionengine/config/foreign_chars.php. For example, take the word ...


3

If you're already using Structure then a simple and straightforward method would be just to create new pages for each language. This might work for you. I used it on a couple of micro-sites and the client was very happy with the results. So your Structure tree might look something like Home - / Products - /products Contact Us /contact-us Polski - /pl ...


3

I thought I'd provide the response that Ellis Lab gave me for this issue, for others who may need it in the future. Unfortunately, it doesn't solve my issue, since rolling back the database at this point really can't be done. The client gets hundreds of new entries into EE2 every couple of days and its been almost a month since the transition. That said here ...


3

Well I worked it out by myself in the end... <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"&...


3

In addition to the tips provided in the link Bhashkar provided, I would strongly recommend you have a look at Low Variables - it's a terrifically powerful add-on that gives you the ability to simultaneously create language-version variables as you create them, which when coupled with the language segment global system variables you'd likely create as ...


2

You can have some guidance from http://www.sidd3.com/multi-language-website-with-expressionengine/ Hope, it would help you.


2

I need multiple-domain support, some e-commerce catalog, uploading files from users and some forum feauteres in future. Is it good choice for this tasks? Yes, ExpressionEngine can do all those tasks, although for multi-domain support you will probably need the Multiple Site Manager (available for purchase separately) , and for the ecommerce you will ...


2

It's not covered in the docs, but apparently, according to this forum post, there are language packs for the forms module to allow you to do this, yes. I'd check in with the DevDemon folks to find out which languages are available and how to go about loading the language pack.


2

This should do it: $accept_language = explode(',',$_SERVER['HTTP_ACCEPT_LANGUAGE']); $lang = $accept_language[0]; echo $lang; switch ($lang) { case 'en-US': case 'en': echo 'Success!'; break; default: echo 'Count on En'; }


2

As long as the template translations are all in place in the module, the default behavior of the segment_x variables should be to default back to their native ExpressionEngine template group / template names as defined in the template manager. In the next version of Transcribe we're also introducing several additional early parse order variables such as {...


2

you're getting that error simply because the https://github.com/EllisLab/EE-Language-Italian pack is for EE 1.x versions. Plus you can download this (though it's not 100% translated) at least it's a Version 2.1.3 https://bitbucket.org/age38dev/eecita/src/87fdcac9ce735f722f4cb182e40f51e42b92b043/2.1.3/EE/language?at=default


2

Just started a repo on Github for a multilingual text fieldtype I'm working on which could help you out, or at least give you some more options : Babeltext


2

The language code within the URL wouldn't break the URL segment for the pages. It would be same as http://yoursite.com/en/segment_1/segment_2/segment_3 You can take a look at Multi Language Website with ExpressionEngine how a multilanguage website can be managed easily.


2

I think I got it to work: With the add-on language prefix option turned on, the add-on prefixes urls with “index.php/es” like this http://domain-name.com/index.php/es, http://domain-name.com/index.php/es/page-name, etc. I created a new template group called “es” and it seems the existing htaccess code that removes “index.php” from templates groups has dealt ...


2

I am not sure if there is any template tag for it but all the languages can be fetched with code. Basically all the language options displayed from the installed language packs within the directory "system/expressionengine/language/". I think, you can develop a small plugin for it with the following code example: ee()->load->model('admin_model'); $...


2

You need to set the language code each time when a page loads. I think, you would know that a language can be set with config variable (within config.php) like: $config['language'] = 'english';. You should have the same logic and use the hook sessions_start. Within the hooked extension you can set the language like $this->EE->config->_global_vars['...


2

Since you're evaluating a string, the arguments should be enclosed in quotes ("). {if "{month}" == "{segment_4}"}class="current"{/if} You may need to add a OR operator for a second condition to check. Update Just realized I misunderstood your question. I found this Multi Language Module that allows you to define phrases ...


2

It's a config item, so you can get it using the Config object, thus: ee()->config->item('deft_lang');


2

Let's take the user_notification_template="" parameter as an example, and your two languages: en and de. (This would work for admin_notification_template="" and recipient_user_template="" as well) First, create two notification templates in Freeform (Notifications tab in the Freeform CP), one in each language. Let's call their short names user_email_en and ...


2

The loop occurs because you're testing again and again and again... Try this: {exp:browser_sniff available_languages="en|zh"} {if browser_sniff_negotiated_language == "zh"} {if browser_sniff_negotiated_language != "{segment_1}"} {redirect="zh/{uri_string}"} {/if} {/if} {/exp:browser_sniff} update Since Transcribe ...


2

Just emailed a fix over to you!


2

It's pretty easy. Create a new Category Field and prefix its name with the language prefix related and use it for the translated name. For example, pt-category_name. On your templates, inside categories variable pair, for example: {if language == "pt"}{pt-category_name}{/if} {if language == "en"}{category_name}{/if}{!-- being `en` your default language --}...


2

Since Publisher doesn't technically have Store support or vise-versa you won't be able to use Publisher for your additional emails directly. You could write an extension that would allow you to either set a custom order status for each language during checkout, which would allow you to assign an email template for their language to that order status. This ...


1

Now, I really don't like this because it would break pages which rely on how segments are placed. For example, if I expected segment_3 to be X data in a page without the two-char language code in the url, adding the language code would break that page. Can't you just have a two character language code for each language, even the default one? This way ...


1

There aren't many solutions that don't require an addon. Here's how I did one recently http://digitalevangelist.net/blog/multi-lingual-expressionengine-practical and here's the one I've used that doesn't need an addon http://cwcrawley.co.uk/2010/01/multi-lingual-websites-in-expressionengine/


1

The 'relationship' is the entry_id. So if you can import the default language, grab the entry id, then import the translated entry and assign the same entry_id it should work. I'm not sure DataGrab would do that out of the box.


Only top voted, non community-wiki answers of a minimum length are eligible