multilingual_sites
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| multilingual_sites [2024/09/13 18:01] – admin | multilingual_sites [2026/03/21 10:11] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Multilingual Sites ====== | ====== Multilingual Sites ====== | ||
| - | The purpose of this feature | + | This feature |
| - | First, navigate to Rotation - Settings - Multilingual | + | Start by creating additional languages in Rotation - Settings - Multilingual. |
| - | You can use [[Google Translate]]. Let’s assume you have added two languages: de and es, for the main site, which is in English. | + | Switch |
| - | The language is switched by adding & | + | **There are 2 ways to display |
| - | There are two options for displaying the preferred | + | 1. Auto Switch |
| - | When the page URL does not change but varies depending on the browser' | + | 2. Auto redirect to existing |
| - | When the page URL changes, | + | |
| - | ===== Auto Switch language ===== | ||
| + | **Auto Switch language** | ||
| - | The script | + | The script |
| - | ===== Auto redirect to existing language | + | **Auto redirect to existing language** |
| - | + | This option redirects | |
| - | The Auto redirect to existing language | + | |
| http:// | http:// | ||
| - | For example, | + | For example, a request to http:// |
| - | To enable | + | To enable |
| - | < | + | < |
| - | RewriteBase / | + | RewriteBase / |
| - | RewriteCond %{REQUEST_FILENAME} !-f | + | RewriteCond %{REQUEST_FILENAME} !-f |
| - | RewriteCond %{REQUEST_FILENAME} !-d | + | RewriteCond %{REQUEST_FILENAME} !-d |
| - | RewriteRule ^([^/ | + | RewriteRule ^([^/ |
| </ | </ | ||
| - | Of course, you can create your own version to accommodate different link variations. | + | Of course, you can create your own URL patterns. |
| - | For each language, there are several options for collecting statistics, mainly differing in two parameters: **Own category stats** and **Own thumb stats**. | ||
| - | If both **Own category stats** and **Own thumb stats** are disabled, you essentially get a simple translation of the site. This approach is beneficial for SEO. | + | **Subdomains** |
| - | **Own category stats** — when it's set to " | + | If you use language |
| - | **Own thumb stats** | + | < |
| + | |||
| + | RewriteCond %{HTTP_HOST} ^([a-z]{2})\.domain\.com$ [NC] | ||
| + | RewriteRule ^ %{REQUEST_URI}? | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | Each language can maintain statistics separately via two options: Own category stats and Own thumb stats. | ||
| + | |||
| + | If both are disabled, you get a simple translation. This is good for SEO. | ||
| + | |||
| + | **Own category | ||
| + | |||
| + | **Own thumb stats** - Gallery thumbnails get separate | ||
| ===== Auto Switch language ===== | ===== Auto Switch language ===== | ||
| - | There is a second | + | This option |
| - | For example, if a user with the DE language | + | When a user with DE language (if configured) visits the site, the page automatically |
| - | To clarify: Auto redirect to existing language | + | To clarify: |
| + | **Auto Switch language** - displays the correct | ||
| ===== Save language preferences ===== | ===== Save language preferences ===== | ||
| - | This option saves the user’s language preference in a cookie. | + | Saves the user's language preference in a cookie. |
| - | If you need to redirect | + | To redirect |
| - | ===== GeoIP-Based Language Detection ===== | ||
| - | The basic language detection method is based on the browser’s language settings. However, it is also possible to configure it based on the user’s country (using | + | ===== GeoIP Based ===== |
| - | To do this, create a language, | + | Beyond browser |
| - | Please note that this setting takes priority. For instance, if you have both FR and DE languages configured, but a user with the DE language | + | Create a language like FR (you don't need translations, but Own thumb stats is required for separate rotation stats). Then decide that traffic from France (and Belgium, for example) should be counted as FR. In the language |
| - | This approach allows | + | This setting takes priority. For example, if you have FR and DE languages, a user with browser language DE but an IP from Belgium will be counted as FR, not DE. |
| + | |||
| + | This lets you group countries together. | ||
| + | |||
| + | Don't create separate rotations | ||
| - | However, be cautious about creating separate rotations for each language. You will need to rotate the database for each group separately, and it's essential to assess whether you have sufficient traffic to support this. | ||
| ===== Translations ===== | ===== Translations ===== | ||
| - | It is fairly simple to translate | + | Translating |
| + | |||
| + | Go to Rotation - CMS Templates - Tpl Custom Var and add custom variables like most_popular. Use these in templates as < | ||
| - | In Rotation - CMS Templates - Tpl Custom Var, add custom variables such as most_popular. This variable can then be used in templates like < | ||
multilingual_sites.1726250485.txt.gz · Last modified: by admin
