Whew – Ok I figured it out. First off thanks Pippin and Peter. The problem is that it apparently confuses some wp plugins if a specific collate hasn’t been declared in wp-config: /** Database Charset to use in creating database tables. */ define(‘DB_CHARSET’, ‘utf8’); /** The Database Collate type. Don’t change this if in doubt. … Read more
Not the first line but the last line could be it. Please check if you have a space after the last ?> sign of your header.php file. Its better suggested that you just remove the last ?> sign as well. So there wont be any headers already sent error generated. And this sort of error … Read more
There is a plugin named Multilingual Press doing exactly what you described. As a lightweight solution, you could create a network table to store the relations and a metabox for all posts where you can search and assign posts from other pages to update the network table. Do not use post meta data. You would … Read more
Well use translation plugin (multilingual Plugins)to create page in english and gujrati. There are a few basic types of multilingual Plugins: 1 Manage multilingual posts in one post per language (e.g. WPML – paid, xili-language, Polylang or Bogo). Translations are then linked together, indicating that one page is the translation of another. 2 Store all … Read more
Post meta is a bad place for translations, because you cannot search by default in these fields, and changing the search to do that results in rather slow and complex queries. What you can do: set up WordPress as a multi-site, use the sub-sites option. Now create a new sub-site for each language, so you … Read more
The localized version is the English version translated. It contains the original and translated strings. You should look for missing translations or badly translated strings. Use a desktop tool like PoEdit or a plugin like Codestyling Localization to manage your WordPress, Themes and Plugins translations (the localized .po and .mo files).
Filter locale if is_admin() is TRUE: is_admin() && add_filter( ‘locale’, function() { return ‘it_IT’; });
You are making wrong assumption here. define(‘WPLANG’, ”); doesn’t mean “original locale of the string” or anything like that, it is taken literally as “no locale specified”. And when it’s nothing WP proceeds to assume default locale, which is en_US. This is why as soon as you add English translations of string they are displayed … Read more
I dealt with this writing a custom template tag. You may want to adjust the structure and classes in order to fit the needs of your styling: function mysite_languages() { if ( function_exists( ‘icl_get_languages’ ) ) : $languages = icl_get_languages( ‘skip_missing=N&orderby=KEY&order=DIR&link_empty_to=str’ ); if ( ! empty( $languages ) ) : echo “\n<ul class=\”languages\”>\n”; foreach ( … Read more
The problem your GET param is using the same name as the query var for your custom post type. $link = $link_aqui_se_sirve.’?’.$establecimientos_cpt_name.’=’.$tax->slug; With that URL, WordPress is expecting the value of the $establecimientos_cpt_name parameter to be a post slug. Instead you are giving it a taxonomy slug. This will give you a 404 unless you … Read more