We’ve just released version 0.9.7 of WPML. This is another bug fix release that includes fixes to problems reported over the last week.
Major new features and bug fixes for WPML 0.9.7
Proper support for posting via XML-RPC
If you’re not sure what XML-RPC is, you can safely skip away.
XML-RPC is a protocol that allows creating and editing contents remotely. Other services that create contents in WordPress use that protocol.
Before version 0.9.7, new posts created with XML-RPC didn’t have a language. This caused problems across the board. Now, they’re assigned to the default language.
Static homepage didn’t display properly when default language argument was used
If you’re using WordPress as a content management system, you’re probably setting the home page as a static page (and another page for the blog). Due to a bug, the translations for that page didn’t display if you’ve used the default language setting (lang=fr). It’s working now.
Added language constants to be used for theme customization
Sometimes, you may want the theme to display differently for different countries (we’ll write more about how to do that soon). Although there was a way to do it, it was a bit of a hack. WPML 0.9.7 adds three constants that can be used in the theme for language dependant customization:
- ICL_LANGUAGE_CODE – the current language code (e.g. fr).
- ICL_LANGUAGE_NAME – the current language name in the current language (e.g. Français).
- ICL_LANGUAGE_NAME_EN – the current language name in English (e.g. French).
This should make theme customization much more straight forward without reverse engineering anything.
Split the cms-navigation.css into structure and design
If you’re using the navigation created by WPML, you’ll love this change. The cms-navigation.css is a rather complex file. It causes the top menus to behave live drop down menus. Since it also includes some hacks to support Internet Explorer 6, it’s even more complicated to understand.
We’ve split that file into two:
- cms-navigation-base.css – this is the structure file. You don’t want to ever edit it as it makes the menus work. It doesn’t include any formating.
- cms-navigation.css – this is the file to edit.
Now that the structural code has been seperated, it’s much easier to customize the navigation. Here is what you need to do:
- Copy cms-navigation.css from /wp-content/plugins/sitepress-multilingual-cms/modules/cms-navigation/css/cms-navigation.css and place it in your own theme’s directory.
- Edit it as much as you like. The file is documented and explains what each section does. It’s pretty short and self explanatory now.
- Make sure that it’s loaded after the <?php wp_head(); ?> call is made (in header.php). This way, your customizations take precedence.
As promised, we’re ready with the customization guide for WPML’s navigation. This guide includes details of the CSS used to style the top down menu, sidebar and breadcrumbs trail.
Thanks for all the feedback, give us more!
Finding and fixing all these problems, in such a short time, was made possible thanks to all the great and detailed feedback we got.
We’re looking forward to the first stable release (1.0) sometime next week. If you see anything that doesn’t look right, let us know about it. Go to our forum and leave a message:
Of course, if you want to give other, non-technical feedback, you’re more than welcome to drop by the feedback page.
Are you already using WPML for live sites?
We’re planning to start a showcase page, showing websites that use WPML. Showcase sites will have a short review text, presenting them to the world, a screen shot and links to the actual site and designer. It’s worth the effort!
If you’re already running a live site and want it featured there, drop us a note. You can use the feedback page or contact us privately.