1. Open your /wp-content/themes/{youratahualpathemename}/bfa_header_config.php file, and find this code:

      bloginfo('url'); echo '/"

   then replace with this following code:

      bloginfo('url'); echo '"

   Please note that part of code located in six different location at that file, so you have to replace it six times.

2. Open your /wp-content/themes/{youratahualpathemename}/bfa_footer.php file, and find this code:

      bloginfo('url'); echo '/"

   then replace with this following code:

      bloginfo('url'); echo '"

3. Open your /wp-content/themes/{youratahualpathemename}/bfa_next_previous_links.php file, and find this code:

      bloginfo('url'); echo '/"

   then replace with this following code:

      bloginfo('url'); echo '"

   Please note that part of code located in three different location at that file, so you have to replace it three times.

That’s all. Now you should have the proper Home’s URL according to their own languages.

1. Go to your cPanel of your website, then choose phpMyAdmin.
2. Choose your WordPress database, and backup your database (as we will modify one of the tables of this database).
3. Click on the SQL tab, and then copy and paste this following SQL update:

   UPDATE wp_icl_translations t, wp_posts p
   SET t.element_type = 'post_page'
   WHERE p.ID = t.element_id
   AND p.post_type = 'page';
    
   UPDATE wp_icl_translations t, wp_posts p
   SET t.element_type = 'post_post'
   WHERE p.ID = t.element_id
   AND t.element_type = 'post';

   Assuming that the prefix of your table is wp_.
   Those 2 statement will update your wp_icl_translations table by replacing “post” become “post_post” for the posts you have already had, and then also replacing “post” become “post_page” for the pages you have already had.

4. Check again your site, and now the posts or your pages will appear properly.
5. If the problem still remains, then it usuallay caused by the older version of WordPress does not support to use WPML version 1.8.0. I have contacted WPML guru about this problem, and still waiting for the solution. Meanwhile, you can try those solutions above.

Hope it helps!

Another information that you need to know is my site uses two languages: English and Indonesian (default language = Indonesian).

So, this is what I did on my WPML 1.8.0:

1. Open /wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php file, and I find this code:

   3399 3400 3401

   }elseif(is_search()){ $url_glue = strpos($this->language_url($lang['code']),'?')===false ? '?' : '&'; $lang['translated_url'] = $this->language_url($lang['code']) . $url_glue . 's=' . htmlspecialchars($_GET['s']);

   then after the last line of that code, I added this following code:

   3403 3404 3405 3406 3407 3408 3409

   }elseif(is_pod_page() ) { // Modified by Masino Sinaga, July 14, 2010 global $slug_en, $slug_id; if ($lang['code']=='en') { $lang['translated_url'] = $slug_en; } else { $lang['translated_url'] = $slug_id; } // Modified by Masino Sinaga, July 14, 2010

2. Open functions.php file that located in my theme that I currently using, and then I added this following code at the top/declaration section of the file:

       global $slug_id, $slug_en;

   those variables important in order to tell WPML that in my Pods template, I use them to get the link from my Pods’ content.

3. In my Pods’ template that I created inside my theme directory, I added this following code:

       global $slug_id, $slug_en;
       $slug_id = site_url().'/propinsi/'.$Record->get_field('slug_id');
       $slug_en = site_url().'/en/province/'.$Record->get_field('slug_en');

   This is only one of the examples how I assign those two variables that mentioned above, so this Pods’ template will hold the values, and then the functions.php file will act as the bridge between Pods and WPML. In other words, the value of variables will be known by WPML that derived from the Pods.

You can see the demo from this following link:
One of the Indonesia Regions. As you can see now, the language switcher (at the right sidebar, also at the bottom of the site) automatically adds the links that came from Pods CMS, either for English or Indonesian.

You will see that those links suddenly just like the links that came from Posts or Pages in WordPress, but they are not. They came from my Pods content, everyone!

Isn’t that great? Oh, how much I love this!

1. Open your functions.php file that usually located inside you theme’s root directory, and then add this function code:

   // In order to display language selector of WPML plugin in footer/header of theme
   function languages_list_footer(){
       $languages = icl_get_languages('skip_missing=0&orderby=code');
       if($l['icl_lso_native_lang']){
           $lang_native_hidden = false;
       }else{
           $lang_native_hidden = true;
       }
       if($l['icl_lso_display_lang']){
           $lang_translated_hidden = false;
       }else{
           $lang_translated_hidden = true;
       }    
       if(!empty($languages)){
           echo '<div id="lang_sel_footer">'; // <-- adjust this "lang_sel_footer" with the style that exists in language-selector.css file that belongs to WPML plugin (based on the version you are currently using).
           foreach($languages as $l){
               if($l['country_flag_url']){
                   echo ' <a href="'.$l['url'].'">';
                   echo '<img src="'.$l['country_flag_url'].'" height="12" alt="'.$l['language_code'].'" width="18" /> ';
                   if(!$l['active']) echo '</a> ';
               }
               echo ' <a href="'.$l['url'].'">';
               echo icl_disp_language($l['native_name'], $l['translated_name'],$lang_native_hidden);
               if(!$l['active']) echo '</a> ';
           }
           echo '</div>';
       }
   }

   Since I used WPML version 1.8.0, then I use lang_sel_footer style that exists in sitepress-multilingual-cms/res/css/language-selector.css file. Please adjust with the style that exists in the related .css file of your WPML.

2. Open your header.php file that usually located inside your theme’s root directory, and add this following code below the .css call:

   <link rel="stylesheet" href="<?php echo WP_PLUGIN_URL; ?>/sitepress-multilingual-cms/res/css/language-selector.css" type="text/css" media="all" />
   <?php languages_list_footer(); ?>

   For example, if you use the TwentyTen theme, then you can put that code above after this following code:

   <link rel="stylesheet" type="text/css" media="all" href="<?php bloginfo( 'stylesheet_url' ); ?>" />

3. Now refresh or reload your site, then you should see now at the very top of your page, that custom footer language switcher appears as we want. If the style does not look good at yours, then the problem is usually caused by the style of the language switcher. Please read and follow the first step above carefully.

Have a nice code everyone, and hopefully this will be helpful!

1. Put this following code to your functions.php file of your current theme:

   // In order to display language selector of WPML plugin in footer of theme
   function languages_list_footer(){
       $languages = icl_get_languages('skip_missing=0&orderby=code');
       if($l['icl_lso_native_lang']){
           $lang_native_hidden = false;
       }else{
           $lang_native_hidden = true;
       }
       if($l['icl_lso_display_lang']){
           $lang_translated_hidden = false;
       }else{
           $lang_translated_hidden = true;
       }    
       if(!empty($languages)){
           echo '<div id="footer_language_list">';
           foreach($languages as $l){
               if($l['country_flag_url']){
                   echo ' <a href="'.$l['url'].'">';
                   echo '<img src="'.$l['country_flag_url'].'" height="12" alt="'.$l['language_code'].'" width="18" /> ';
                   if(!$l['active']) echo '</a> ';
               }
               echo ' <a href="'.$l['url'].'">';
               echo icl_disp_language($l['native_name'], $l['translated_name'],$lang_native_hidden);
               if(!$l['active']) echo '</a> ';
           }
           echo '</div>';
       }
   }

2. Open your header.php file of your current theme, and find this code:

   <?php } ?>
   <?php include (TEMPLATEPATH . '/functions/bfa_meta_tags.php'); ?>

   before the first line of that code, please insert this following code:

   <link rel="stylesheet" href="<?php echo WP_PLUGIN_URL; ?>/sitepress-multilingual-cms/res/css/language-selector.css" type="text/css" media="all" />

   this is important, in order to include the .css file belongs to WPML plugin.

3. The next step, you have to call that function in your sidebar or any bar of your current theme. For example, I use Atahualpa theme, then I put this code calling in the “footer.php” file:

   <?php languages_list_footer(); ?>

   after this following line:

   <?php wp_footer(); ?>

4. If you want to see the output or demo of this modification, you may visit this following site: Wilayah Indonesia, then please scroll your mouse to the bottom of the page (footer), you will see there are two languages, English and Indonesia.
5. Another similar modification with that above, I also have created the custom language switcher in the sidebar of my theme. I put this following code in “footer.php” of my current theme:

   <?php do_action("icl_language_selector"); ?> // call the language selector

   after this following code:

   <!-- Right Sidebar -->
   <td id="right">

In order to display the output of the language switcher properly using the original css of WPML, then we have to put that css calling above. And don’t forget to always include the .css file that belongs to WPML plugin inside your header.php file in order to display the language selector properly.

If you wan to get the value of those three constants, then you can put this code to your index.php file of your current theme.

<?php 
  echo "<br />Language Code: ".ICL_LANGUAGE_CODE; 
  echo "<br />Original Language Name: ".ICL_LANGUAGE_NAME; 
  echo "<br />Language Name in English: ".ICL_LANGUAGE_NAME_EN; 
?>

Suppose you are using English (en) and Indonesian (id) language, and you want to check the current language code only, so you can execute the certain code related to the current language code, then you can use this following code:

<?php
  if (ICL_LANGUAGE_CODE == 'en') {
    // put your code here if the current language code is 'en' (English)
  } elseif (ICL_LANGUAGE_CODE == 'id') {
    // put your code here if the current language code is 'id' (Indonesian)
  }
?>

Hopefully this will be helpful.

Here is the comparison between qTranslate and WPML:

Advantages of WPML:

1. The database contents for posts remain unmodified (easy install and uninstall).
2. Everything gets translated by default. If a post includes custom fields, they’re attached to that post, so they are already associated with the language.
3. Other plugins that analyze contents (like related posts) keep working correctly.

Disadvantages of WPML:

1. More complex architecture. The plugin needs to hook to many WordPress functions and filter them so that only contents that matches the language is returned.
2. Additional tables are required – normally, to hold the translation grouping.

Advantage of qTranslate:

1. Side by side editing is easily implemented.
2. Less things to break. There are no additional tables and much fewer things to modify in WordPress.

Disadvantages of qTranslate:

1. In order to create multilingual contents, the user needs to insert the language tags manually, to everything the plugin doesn’t hook to. Example: Adjust MicroKid Related Posts with qTranslate Plugins
2. Uninstall can be complicated, as the database needs to be cleaned from multilingual contents.

Choosing the most suitable multilingual Plugin for your needs will take some time.

In any case, installing a multilingual plugin is a big change for any site. It would be a good idea to first create a test site and verify that everything works correctly between all the required plugins and the theme and only then install.

Since any multilingual plugin changes the database significantly, doing a database backup is required before experimenting. Have a nice test!

Credits: Multilingual WordPress