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


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

ExpressionEngine does not have multi-lingual features in its base configuration, but you can add these via an add-on: there are at least two very good options available. Publisher Transcribe Both are powerful multi-lingual solutions that make it possible to build and manage true multi-lingual sites. Both are from well respected commercial providers, are ...


1

okay it seems you are into this too. if you want to spend 200$ use https://boldminded.com/add-ons/publisher-2 if not; here is the tips for an easy way to do it. lets say that you have two languages English - en Arabic - ar first duplicate your fields in your channels and make sure that you suffix the field name with the short-code of your language Like: {...


1

it's to do with parse order. something is mixed up.Can you try addin a parse="inward" to the exp:channel:entries or the exp:transcribe:replace tag?


1

Using template groups for different language identifiers is always going to be limiting and not easily scaleable, but to resolve your issue I'd suggest a redirect plugin that takes the user to a specific template that then decides where to take them: Login Redirect But not sure what you're going to use as an identifier to know where to take them...? The ...


1

If the city/country is the only thing you are translating it might be easier to use a 3rd party service to translate them, such as geonames.org. e.g. http://api.geonames.org/search?name=moscow&country=RU&featureCode=PPLC&maxRows=10&type=rdf&username=demo The demo name has reached its API limit, here is what the response looks like:


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

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