Open ps_auto_sitemap.php file, and find this code:

233
234
235

   foreach( $category_posts as $post ) {
     $post_list_in_category .= "\t" . '<li class="post-item post-item-' . $post['ID'] . '"><a href="' . get_permalink( $post['ID'] ) . '" title="' . attribute_escape( $post['post_title'] ) . '">' . wp_specialchars( $post['post_title'] ) . "</a></li>\n";
   }

replace with:

233
234
235

   foreach( $category_posts as $post ) {
     $post_list_in_category .= "\t" . '<li class="post-item post-item-' . $post['ID'] . '"><a href="' . get_permalink( $post['ID'] ) . '" title="' . attribute_escape( wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage( ( $post['post_title'] )))) . '">' . wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage( $post['post_title'] )) . "</a></li>\n";
   }

There was one special note that important to know (for those of you who have just used this plugin for the very first time). Perhaps, you will get confused (actually, this was also happened to me) when you see this plugin’s setting from admin panel. There is a PostID of the sitemap directive there. PostID here has the meaning as Page ID that you have to created first, since this site map content would be located on that page. I suggest to the author of this plugin, IMHO it would be better if we called it as PageID instead of PostID.

Now, let us back again to the main topic. After you create a new page, then please add this tag in the page content, while you are in HTML mode:

<!-- SITEMAP CONTENT REPLACE POINT -->

and then save this page. Afterwards, go to the list of your pages in admin panel. You will see from your list of the pages, the ID number of that new page you have just added. Enter that page ID to the PostID of the sitemap, and your site map is ready to use! That’s so simple, right?

This has been tested and working good in PS Auto Sitemap version 1.1.3 and qTranslate version 2.4.3.

1. You can now add drafts and planned posts as related posts, without them appearing on your site before they are properly published.
2. Added shortcode support: you can now place the [ related-posts ] shortcode within the content of your post to display the related posts anywhere you want.
3. (For advanced users) Added a parameter to the MRP_get_related_posts function to optionally get the related posts in an object, so you can easily use it in other plugins or your own custom way of displaying the list of related posts. For documentation on this, see [the API section](http://www.microkid.net/wordpress/related-posts/#API “Microkids Related Posts API functions”).
4. (For advanced users) Added a parameter to the MRP_get_related_posts function to optionally include unpublished posts to the related posts list. For documentation on this, see [the API section](http://www.microkid.net/wordpress/related-posts/#API “Microkids Related Posts API functions”).

After the automatically-upgrade process was completed, I remembered that I had modified this Microkids Related Post plugin before via this article: Adjust MicroKid Related Posts v2.3 with qTranslate v2.4.3 Plugins. It meant that I had to adjust its new script again in order it compatible with qTranslate plugin.

So here was I made:

1. Open mrp-search.php file, find this code:

   52	foreach( $results as $result ) {

   replace with:

   52 53

   foreach( $results as $result ) { $related_post_title = wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($result->post_title));

   find this code:

   60	echo $result->post_title;

   replace with:

   60	// echo $result->post_title;

   find this code:

   64	echo '</a> <a href="'.get_permalink( $result->ID ).'" title="View this post" class="MRP_view_post" target="_blank">&rsaquo;</a></li>';

   replace with:

   64	echo $related_post_title.'</a> <a href="'.get_permalink( $result->ID ).'" title="View this post" class="MRP_view_post" target="_blank">&rsaquo;</a></li>';

   then save this file.

2. Open microkids-related-posts.php file, and find this code:

   104	echo '<li id="related-post-'.$related_post->ID.'"><span>'.$post_title.'</span><span><a class="MRP_deletebtn" onclick="MRP_remove_relationship(\'related-post-'.$related_post->ID.'\')">X</a></span>';

   replace with:

   104	echo '<li id="related-post-'.$related_post->ID.'"><span>'.wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($post_title)).'</span><span><a class="MRP_deletebtn" onclick="MRP_remove_relationship(\'related-post-'.$related_post->ID.'\')">X</a></span>';

   find this code:

   328 329 330 331 332

   $output .= "<ul>\n"; foreach( $related_posts as $related_post ) { $output .= "<li><a href=\"".get_permalink( $related_post->ID )."\" title=\"$related_post_title\">".$related_post->post_title."</a></li>\n"; } $output .= "</ul></div>\n";

   replace with:

   328 329 330 331 332

   $output .= "<ol>\n"; foreach( $related_posts as $related_post ) { $output .= "<li><a href=\"".get_permalink( $related_post->ID )."\" title=\"$related_post_title\">".wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($related_post->post_title))."</a></li>\n"; } $output .= "</ol></div>\n";

   find this code:

   375 376 377 378 379

   echo "<ul>\n"; foreach( $related_posts as $related_post_id => $related_post_title ) { echo "<li><a href=\"".get_permalink( $related_post_id )."\" title=\"$related_post_title\">".$related_post_title."</a></li>\n"; } echo "</ul></div>";

   replace with:

   375 376 377 378 379 380

   echo "<ol>\n"; foreach( $related_posts as $related_post_id => $related_post_title ) { echo "<li><a href=\"".get_permalink( $related_post_id )."\" title=\"$related_post_title\">".wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($related_post_title))."</a></li>\n"; } echo "</ol> </div>";

This has been tested and working good in Microkids Related Posts version 2.4 and qTranslate version 2.4.3.

1. Go to your admin panel, then click on Settings -> General
2. At the Blog Title directive, add the language tag. For example, your Blog Title is: My First Website. Change it become:
   [:en]My First Website[:id]Situs Pertamaku
3. At the Tagline directive, also add the language tag. For example, your Tagline is: This is my first website. Change it become:
   [:en]This is my first website[:id]Ini situs pertamaku
4. Save your settings by click on Save Changes button at the bottom of the page.

Now, when you choose English as the current language from your language selector, then it will show you as:

My First Website
This is my first website

and when you switch its language become Indonesian language, it will show you as:

Situs Pertamaku
Ini situs pertamaku

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

Today I started to use MicroKid Related Posts plugins for displaying the Related Posts at the bottom of the post. Unfortunately, I found a little bit problem after I have succeeded to implement this plugins. What was that? Well, since the post title has been saved by qTranslate plugins in one field in wp_posts table for all active languages, then each time the post title displayed, it contains of the title post belong to those all languages, and there is no space between them.

For example: I already have a post with title in English “Welcome to My World” whereas in Indonesian language this has the meaning as “Selamat datang di Dunia Saya”. For those of you who has not tried this plugins, the value for the post_title field would be like this:

<!--:en-->Welcome to My World<!--:--><!--:id-->Selamat datang di Dunia Saya<!--:-->

that is why when it displayed the result will become like this:

“Welcome to My WorldSelamat datang di Dunia Saya”

whereas between one title with another belongs to other language does not separated by space character, and I think this is something that looks like not so good.

When I search this post and then select this post title as related post for my new post, then the title of this related post will become: “Welcome to My WorldSelamat datang di Dunia Saya”. As you can see, that post_title being shown contains of the both active language; English and Indonesian. I think it would be better if it should be like this:

Welcome to My World if the selected language is English,
or:
Selamat datang di Dunia Saya is the selected language is Indonesian.

This is an interested challenge for me. So I started to search the script related to this, and trying to make it came true.

So, here was I made:

1. Open mrp-search.php file belongs to MicroKid Related Posts plugins, and find this code:

55

foreach( $results as $result ) {

then replace with this:

55
56

foreach( $results as $result ) {
  $related_post_title = wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($result->post_title));

also, find this code:

63
64

echo $result->post_title.'</a> <a href="'.get_permalink( $result->ID ).'"
     title="View this post" target="_blank">&rsaquo;</a></li>';

and replace with this:

63
64

echo $related_post_title.'</a> <a href="'.get_permalink( $result->ID ).'"
     title="View this post" target="_blank">&rsaquo;</a></li>';

We have done with the mrp-search.php file.

2. The next step is that we have to edit the code in microkids-related-posts.php file.
Open the file and find this code:

95

foreach( $related_posts as $related_post_id => $related_post_title ) {

replace with this:

95
96

foreach( $related_posts as $related_post_id => $related_post_title ) {
  $related_post_title = wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($related_post_title));

also, find this code:

317

foreach( $related_posts as $related_post_id => $related_post_title  ) {

and replace with this:

317
318

foreach( $related_posts as $related_post_id => $related_post_title  ) {
  $related_post_title = wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($related_post_title));

then, find also this code:

367

foreach( $related_posts as $related_post_id => $related_post_title  ) {

and replace with this code:

367
368

foreach( $related_posts as $related_post_id => $related_post_title  ) {
  $related_post_title = wp_specialchars(qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage($related_post_title));

That’s all. Now the title post in Related Posts section will look better than before. You can see the result in the bottom of this post at the Related Posts section, when you display a post with full-mode.

This has been tested and working good in MicroKid Related Posts version 2.3 and qTranslate version 2.4.3.

Then after serveral hours surfing through the Internet, I found a WordPress plugins that has the ability to switch/translate the content of a page to the selected language. The plugins’ name is qTranslate that you can find from here: http://wordpress.org/extend/plugins/qtranslate/ . I downloaded qTranslate version 2.4.3 that compatible with WordPress version 2.8.4 or later.

Incredible! This plugins is really useful as I have been looking for. The most important thing that I like from this plugins is: user will become easier while creating a new article, since there was new tabs as many as the language that being enabled or used. Therefore, we can switch from one to another tab to translate to the new language only from one form.

Another advantage that you get when you use this plugins is: every post for all active languages will be saved in one record. Thus, this will keep your database size smaller, than if every post for each language will be saved in separate record.

But, it has small weakness, especially if you deactivate this plugins after you have some posts that added or updated with this multi-language feature. The tag as I mentioned above will be displayed since it was located in one field. Therefore, if you want to use or currently using this qTranslate plugins, please reconsider not to deactivate it after you have posts that made with this plugins. Except if you want to spend your time to edit the field contains of that separator tag in database.

Now, I am starting to use WordPress, and had fallen in love with it since I knew and found this qTranslate plugins.