As per Theme Handbook ⇒ Internationalization, you should call load_child_theme_textdomain() from within the after_setup_theme hook: function load_greattheme_textdomain() { load_child_theme_textdomain( ‘greattheme’, get_stylesheet_directory() . ‘/languages’ ); } add_action( ‘after_setup_theme’, ‘load_greattheme_textdomain’ ); Make sure you name your *.mo and *.po files properly (follow the link above).
You must change the WordPress permalink settings. Go to Settings>Permalink and chose “post name” and save then reload the Polylang settings and the options should be available. I have not tried it with other permalink settings, but it cannot be “plain” which is the default. It took me 2 hours to figure this out…
I cant test my .po file for Turkish Language
For multiple languages, two wordpress instances on subdomains or a plugin?
Yes, it is extremely frustrating to find a plugin that works without errors and is still customisable. I have tried the following: Shopp – www.shopplugin.net (very good, but will only support WPML in the next update – unknown release date) Marketpress – http://wordpress.org/extend/plugins/wordpress-ecommerce/ (workes well, but is pretty limited, not sure if the paid version … Read more
Woah, default Polish WordPress package is corrupted. Change define(‘WPLANG’, ‘pl_PL’); to define(‘WPLANG’, ‘pl_pl’); or download older version.
well , while dealing with chinese characters – there are MANY problems that can cause this , but many times , it is as simple as the encoding of the php files. (simple as a figure of speech – you will soon understand why ) A PHP file is a TXt file . and even … Read more
In your wp-config.php set the encoding constants correctly: define( ‘DB_CHARSET’, ‘utf8’ ); define( ‘DB_COLLATE’, ‘utf8_general_ci’ ); And add an accept-charset attribute to your form: <form name=”frm” method=”post” action=”<?php bloginfo(‘url’); ?>/message/” accept-charset=”utf8″ >
Take a look at get_blog_permalink
The before_widget and after_widget notices can go away with ease if you send those as params to the function you are using to call the Transposh widget Update: recent version (0.9.0) fixed those notices