After a brief trial stage of this new release of WordPress, here is a new post about what I had to customize, why I had to do it and what is the final outcome of the operation.
With my previous blog I proposed, as a case study, to implement a multilingual blog which could be easy to maintein. To get this result, after many searches, I resorted to the xLanguage plugin. At first this appeared as the right choice, but at last – also due to the coupling whit other WordPress plugins, especially whit WP Super Cache – it revealed to be tricky (e.g., if the cache was regenerated by some crawler’s visit, the resulting static pages were made up by mixed localizations, so I had to clear and regenerate the cache by hand) and difficult to keep working when coupled with other plugins, because I had to patch many plugins to work with xLanguage tags (but I had to reapply my patches at every update of the plugins). Frustrating and not very effective.
With the release of WordPress 3.0 and the possibility to enable its multisite mode, I wanted to try to manage the different languages of the blog as distinct subsites, with a common theme and plugins, but correlating the blogs and the article/pages one to each other based on their languages using a pair of custom fields to be accessed by some minimal customizations to the theme.
Here you find the few lines of code required to obtain what I wanted, with the path to the file to edit in bold face.