Believe it or not, if you are running a multilingual site using Atahualpa theme and WPML plugin, you will find that there is a double trailing slash in the Home’s URL that generated by WPML, especially for Home’s URL belongs to the languages other than the default one and you are using the “directory per language” setting in WPML. This can be happened since Atahualpa add a trailing slash in every Home’s URL when the home page is being displayed, whereas WPML also added another trailing slash after the language code in the URL. So, this will make a double trailing slash in the Home’s URL. In order to remove one of these trailing slash, you can use this following modification. As time goes by, this modification being applied into Atahualpa version 3.5.3 (the last version while I was writing this article) and WordPress version 3.0.1. I am not sure whether this modification can be applied into the older versions. Read more…
The modification I made in the article with titled: How To Make Breadcrumb NavXT Plugin Support for Multi Language will make that plugin will support for multilingual site. Unfortunately, the Home link in the breadcrumb (if you display it in the breadcrumb) will give you a result always pointing to the default URL’s home, and not to the home of the selected language. For example, you have a multilingual site which English as default language and Indonesian as the second language. So, the default of URL’s home in English is http://www.example.com, and unfortunately the URL’s home in Indonesian does not change, and still using: http://www.example.com instead of http://www.example.com/id/. In order to overcome this little issue but still annoying me, then this following modification will help you by replacing only two lines of code in the breadcrumb_navxt_class.php file belongs to Breadcrumb NavXT plugin. Read more…
For those of you who encountered the missing posts/pages after upgrading your WPML plugin to 1.8.0 version, then this following solutin might be help you. Since WPML changed the element_type value of post and page in the icl_translations table, ie each into post_post and post_page, then you have to adjust this value at the element_type field. After doing comparison to several version of WMPL, I found out that this changes happened since WPML version above 1.7.7. In version 1.7.7, this field was still using post and page instead of post_post and post_page. Actually, when you upgrade your WPML to 1.8.0, this value will be automatically adjusted to the new value. But, in some cases, there are some websites that do not automatically turn to the new value, especially if they deactivate and activate the plugin manually (because they upgrade by replacing the files manually, and not using the auto-update feature). Read more…
If you use Pods CMS plugin with Atahualpa theme for your WordPress-based site, then this following modification is for you, indeed. It will show you how to display the Pods data properly by using Atahualpa theme in WordPress site. Atahualpa is one of the best WordPress theme that I have been using for this last one year. It is a very powerful theme. However, for some beginners, this theme looks too complicated, especially if you want to hard-code the source in order to put your own content into its sidebar. For example, in this case that we are talking about, when you add your own Pods data into the middle-area of your site, the sidebars are messed-up. Then, after for several hours exploring this theme, I found the trick how you can add your Pods data easily by modifying one of the theme’s files, afterwards adding your own template files and put them inside the Atahualpa theme directory. Yay! That’s so simple, huh? Read more…
WPML is a plugin which has the ability to turn your WordPress site into complete multilingual content management systems. Unfortunately, until now I meant, at least until the time before I found this following solution, WPML only supports for the translation of the WordPress original content, such as: posts, pages, categories, tags, and menus (since WordPress version 3.0). I can understand about this, since there are so many possibilities about the content you may have in Pods CMS! That is why WPML has not supported for Pods CMS plugin, yet, whereas this feature I have been looking for that could be implemented in WPML too. I have been waiting for such long time, and… today… God bless the day I found this following solution, indeed! Although the following modification I made sounds like a little tricky or hackish into the WPML’s code, but it works very fine at mine. So, if you are using Pods CMS and WPML for your WordPress site, and you want to add your own translation link that came from your own content in Pods CMS into the language switcher that belongs to WPML, then you came to the right place, because this modification is only for you! Read more…
I saw one of the interesting discussion topic on the WPML Forum about the same thing with the title of this article. By accidentally, I have just modified the custom footer language switcher for one of my websites that using multilingual feature, and also wrote the similar article about it a few days ago on this my blog. Thanks for the topic on the forum, so I can do some exploration in order to implement the solution for the question that has been asked on the forum. So here is the solution I made for it. Read more…
This following modification will change the javascript files that belong to WordPress core, in order to make the Link tag in WordPress post/page editor become open in new tab/window by default. As we know, by default in WordPress, this tag will open in the same window since there is no target=”_blank” property in the a href, especially if you insert this tag by typing your post/page from HTML tab (not from Visual tab) on your WordPress’ post/page editor. As this will change the core file of your WordPress, then you have to change the related files if you upgrade your WordPress core installation. So, please be kind, everyone! Read more…
Today I found something that annoying me when I tried to test the security hole by displaying the theme directory for one of my website that using Atahualpa theme version 3.5.1. Some error messages appeared when I tried to access such address: h++p://www.mydomain.com/wp-content/themes/atahualpa351/ . This error message caused by the using of unknown TEMPLATEPATH constant if this file accessed directly without from the index of the website itself. So, here is the modification I created to display “Access denied” message instead of error message that displaying the path of the theme directory in my web server. Read more…
I have just modified the custom language switcher for one of my websites that uses multi language feature by using WPML plugin and Atahualpa theme. I saw the related code to implement it via this following article: Custom Language Switcher. Unfortunately, since WPML has upgraded its version for several times, the “languages_list_footer()” function in that article should be changed in order to compatible with the last version of WPML, including the “lang_native_hidden” and “lang_translated_hidden” parameter that will be used in the “icl_disp_language” function. So here is the modification code that I have created in order to display it in the footer of my theme. Read more…
Yesterday, I successfully modified the MicroKid Related Posts version 2.5 plugin became support for multi language. I edited the strings that still did not use the gettext function, added the sub directory named “languages”, and then added the .mo file into it. I have created the Indonesian translation file into that sub directory. So, there is one .mo file at the moment. I have implemented this multi language version into one of my sites that support for multi language. I hope the author of this plugin will add this multi language feature into the next release. Read more…
Recent Comments