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

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"&...


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

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

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

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

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


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

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

At its core, Transcribe provides three main functions for translating websites: It lets you set up languages and will detect from the URL which of those languages the user wants. It allows you to have different language versions of the same channel entry (e.g. About Us and Over ons) and (using step 1) gives you the correct language version in your {exp:...


1

Without this going into an opinion based answer, the major factors will be project budget and SEO performance. The latter URL structure is far better for SEO purposes and also for your audience (seeing the URL in their native language). To clarify this is the better URL Structure for this: domain/en/about-us domain/fr/a-propos-de-nous Note: There are even ...


1

There's a comment on EE Insider that may be useful to you. It has been contributed by ignitesystemsltd. Thanks for that! Our client wanted a multi language URL_TITLE which would at first seem to be impossible out of the box with the built in URI handling. BUT we overcame this by a simple mechanism: On the page template that renders the singular ...


1

I haven't used Bieber's add-on, but, from glancing at the docs, I believe you should use their {language_code} variable to feed CE Cache's url_prefix parameter (had to do something similar using Publisher on a multilingual site). Something like this should do it, I think... maybe: {exp:ce_cache:ic url_prefix="{language_code}" ...}


1

I think you emailed me about this, and it might be a bug when that variable is inside of a snippet as it appears to work when its in a template file directly.


1

what you can do is to add some transcribe variables so you can generate language codes. make on like transcribe_lang_country with the value "en" and one like transcribe_lang_language with the value "US" (this is for the american english language version. I don't know the spanish ones) then let the locale be determined by the browser by adding the country ...


1

You can try the Publisher add-on, it supports both Playa and Matrix. More information can be found on the boldminded.com website.


1

Publisher - it offers the most flexibility - especially in having URLs relative to the language (good for native users and for SEO), easy toggling between language entries. This also neatly handles rewriting for custom language identifiers in the URL. Although you can roll your own solution, using tips and tricks found elsewhere and something like Republic ...


1

Well, this looks like it is going into the discussion direction, but I will chip in my thoughts on this anyhow. We are also right now in the process of thinking about on how to best turn an EE and CT powered ecommerce into a multi-language site. I believe to have researched all apporoaches out there and at the moment I tend to devide the sites in different ...


1

I think, you would like to show the Date (like day, month name) in different languages. Right? If you are using language pack for multi-language then you can change those into language file "system\expressionengine\language\english\core_lang.php". This is for English, you can do same for other language.


1

The way I read the documentation on session hooks, what you set in sessions_start gets overridden by the logged in users settings. Here is what the documentation says exactly: "Reset Session class variables, modify default/guest settings, take over whole session check, etc." From what you're saying, I think you need your code on the sessions_end hook. Doc: ...


1

These special variables are only used in the Member module and Search module on the front-end - they won't be parsed anywhere else. Why, I do not know. To see what they correspond with, take a look at this snippet from the Search module code: // Parse lang variables $swap = array( 'lang:total_search_results' => lang('...


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.


1

Doing a similar thing for a site now and here's what we're doing: Enable the IP to Nation module Install and activate the Clive Zagno ipgeo plugin Add code below to EE - we put it in a snippet snp_html-header Set Transcribe to always use a language abbreviation in the url {if "{transcribe:language_abbreviation}" == "es"} {if "{exp:ipgeo:code}" != "ES"} ...


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