{"id":2320,"date":"2009-08-18T23:25:58","date_gmt":"2009-08-18T23:25:58","guid":{"rendered":"http:\/\/wpml.org\/?p=2320"},"modified":"2009-08-18T23:25:58","modified_gmt":"2009-08-18T23:25:58","slug":"multilingual-atahualpa-theme","status":"publish","type":"post","link":"https:\/\/wpml.org\/pt-br\/tutorials\/2009\/08\/multilingual-atahualpa-theme\/","title":{"rendered":"Multilingual Atahualpa theme"},"content":{"rendered":"

\"atahualpa<\/a>I’m<\/strong> going to show how to use Atahualpa<\/a>, by Bytes For All<\/a>, for building multilingual WordPress sites using WPML.<\/strong><\/p>\n

A theme for a multilingual WordPress site needs to have all strings wrapped in gettext calls, but it’s not quite enough. Using gettext in the theme allows it to display in a different (single) language from what it was originally built with.<\/p>\n

To run multilingual, the theme needs to to allow visitors to choose their display language and deliver the correct content per language.<\/p>\n

A multilingual version for Atahualpa<\/h2>\n

Let’s start at the end. Here is a demo site powered with a modified version of Atahualpa<\/a> and here is the modified theme<\/a> which you can download and use.<\/p>\n

What we changed to make Atahualpa multilingual<\/h2>\n

1. Adding wpml-integration.php to the theme’s directory<\/h3>\n

wpml-integration.php is found in WPML’s directory under docs\/theme-integration<\/em>. It includes a collection of functions which help turn themes into multilingual.<\/p>\n

All these functions are designed to make themes use WPML if it’s active or ignore it if it’s missing. This means that the theme would run multilingual if WPML is available or normally (single language) otherwise.<\/p>\n

Added to functions.php<\/strong>:<\/p>\n

include dirname(__FILE__) . '\/wpml-integration.php';<\/pre>\n
This statement loads wpml-integration.php and makes it available to all the files in the theme.<\/p>\n
2. Adding language selectors<\/h3>\n
Language selectors make it possible for visitors to choose the language in which the site is displayed. Often, it’s a good idea to add several types of language selectors. Visitors scan the site quickly and look for visual hints to contents in their languages. Different people look at different places, so adding different types of language selectors to different parts of the page will help move visitors find their language.<\/p>\n
We added WPML’s drop-down language selector to the sidebar by adding it to header.php<\/strong>:<\/p>\n
<?php wpml_languages_selector() ?><\/pre>\n
\"atahualpa_drop_down_language_selector\"
Drop down language selector<\/figcaption><\/figure>\n
We also added a horizontal list of languages to the site’s footer. Many users first scroll all the way to the bottom to see what’s there (and how long pages are), so it’s a good place to tell pages are available in other languages. We added the following code to footer.php<\/strong>:<\/p>\n
<?php wpml_languages_list() ?><\/pre>\n
\"Horizontal<\/em>
Horizontal language selector in footer<\/figcaption><\/figure>\n
Finally, we added a language selector at the end of each post. This adds a sentence to each post, telling in what other languages it’s available. Added the following to index.php<\/strong> (which includes a custom version of WordPress’ display loop):<\/p>\n
<?php if(is_singular()) wpml_content_languages(); ?><\/pre>\n
\"List
List of translation languages<\/figcaption><\/figure>\n
3. Making the home page link go to each language’s home<\/h3>\n
When visitors click on ‘Home’, they expect to get to the home page without switching language. Since each language has a ‘home page’ with a different URL, a single value for all will not work.<\/p>\n
Normally, WordPress themes calculate the address for the ‘Home’ page based on the ‘Blog URL’ value set in the admin page. WPML created a function that calculates the correct home address according to the display language.<\/p>\n
We replaced get_option(‘home’)<\/strong> with wpml_get_home_url()<\/strong>. Also, the get_option(‘home’) function returns the site’s localication without a trailing slash (\/), so themes add it manually. WPML’s function includes this slash (there’s a long story behind this).<\/p>\n
To do this change, we had to edit two files. Modified functions\/bfa_get_options.php<\/strong> and change:<\/p>\n
$bfa_ata['get_option_home'] = get_option('home');<\/pre>\n
into<\/p>\n
$bfa_ata['get_option_home'] = wpml_get_home_url();<\/pre>\n
Also, edited functions\/bfa_header_config.php<\/strong> and removed the trailing slash from the home page link:<\/p>\n
'<a href=\"' . $bfa_ata['get_option_home'] . '\">' . $bfa_ata['bloginfo_name'] . '<\/a>'<\/pre>\n
4. Really advanced – translating texts users enter in the theme admin screen<\/h3>\n
Atahualpa allows controlling some texts through the admin screen. This is a great thing which allows to manage the site without editing PHP files. WPML can translate these strings too using its String Translation mechanism.<\/p>\n
To do this, the theme needs to tell WPML which strings need to be translated and then display the translation if it exists.<\/p>\n
When users go to the theme’s admin screen, update the texts and click on Save, the function bfa_ata_add_admin<\/strong> from functions\/bfa_ata_add_admin.php<\/strong> is executed. We added the following section to it (starting at line 11):<\/p>\n
global $wpml_translatable_strings;\r\n foreach($wpml_translatable_strings as $wpml_str ){\r\n\u00a0\u00a0 if(isset($_REQUEST['bfa_ata_'.$wpml_str]) && trim($_REQUEST['bfa_ata_'.$wpml_str])){\r\n\u00a0\u00a0\u00a0 wpml_register_string('atahualpa theme', $wpml_str, stripslashes($_REQUEST['bfa_ata_'.$wpml_str]));\r\n\u00a0 }\r\n }<\/pre>\n
What this does it run through a list of strings defined in the global variable $wpml_translatable_strings<\/strong>. It registers each string in WPML’s string translation list.<\/p>\n
The first argument is the context for the strings. Any name would go, but you should select a name that describes the strings. The second argument is the name for the string (doesn’t get translated). The last argument is the value of the string – gets translated.<\/p>\n
To display the translations (if they exist), we added the wpml_t<\/strong> function to functions\/bfa_get_options.php<\/strong> (starting at line 204):<\/p>\n
global $wpml_translatable_strings;\r\nforeach($bfa_ata as $k=>$v){\r\n\u00a0\u00a0 if(in_array($k, $wpml_translatable_strings) || $__first){\r\n\u00a0\u00a0\u00a0 $bfa_ata[$k] = wpml_t('atahualpa theme', $k, $v);\u00a0\u00a0\u00a0 \u00a0\r\n\u00a0 }\r\n}<\/pre>\n
This code is run when the site is displayed to visitors. It will loop through the list of strings, check if it’s been registered for translation (in_array<\/strong>) and if so, get the translation. The wpml_t<\/strong> function will return the translated string in the current language, if translation exists, or just return the original string if there’s no translation.<\/p>\n
Turning other WordPress themes multilingual<\/h2>\n
We’ve already done similar work on iNove<\/a> and Arras<\/a> and are planning to convert more themes to multilingual.<\/p>\n
Our intention is to provide ready-to-use multilingual themes and help you build your own multilingual-ready themes. Using the techniques we described here, you can build themes that will run multilingual when WPML is available or in a single language without WPML.<\/p>\n
If you’re building themes and need help turning them multilingual, feel free to open new threads in the forum<\/a>.<\/p>\n
You can also make money (really passive income) by adding multilingual support to your themes. We’ll talk about including affiliate IDs in themes in the next post.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’m going to show how to use Atahualpa, by Bytes For All, for building multilingual WordPress sites using WPML. A theme for a multilingual WordPress site needs to have all strings wrapped in gettext calls, but it’s not quite enough. Using gettext in the theme allows it to display in a different (single) language from […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"ep_exclude_from_search":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-2320","post","type-post","status-publish","format-standard","hentry","category-tutorials"],"_links":{"self":[{"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/posts\/2320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/comments?post=2320"}],"version-history":[{"count":19,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/posts\/2320\/revisions"}],"predecessor-version":[{"id":2343,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/posts\/2320\/revisions\/2343"}],"wp:attachment":[{"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/media?parent=2320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/categories?post=2320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpml.org\/pt-br\/wp-json\/wp\/v2\/tags?post=2320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}