Sun 10 Dec 2006
Gengo: Compatibility
Posted by Jamie under Development News.
Plugins that do and don't work with Gengo.
Some plugins are incorrectly localized and don’t work with Gengo. If you see an error message on your blog, deactivate all plugins but Gengo, then reactivate them, one by one, to see if one of them is broken. The following plugins are known to have had some problems in the past, which now may or may not be fixed:
- WordTube V1.42
- Gallery 2 (?)
- runPHP 2.2.2
- WP-ContactForm 1.4.3 (oggg in the forum)
- DB Backup v.2.0
- Sociable 2.0: move line 31 to 536
- Google Sitemaps 2.7 (works in version 3.0b6)
- Ultimate Google Analytics 1.5.2 (works in v1.5.3)
- Spam Karma 2.2 (Spam Karma 2.3 is compatible with Gengo.)
If you have something to add to the list, feel free to leave a comment!
The main cause of incompatibilities with Gengo is this line:
load_plugin_textdomain(<plugin_name>, <locale_path>);
If you see this line near the top of the plugin file, that is probably the reason the plugin won’t work with Gengo. Just like the code that adds widget-capabilities to plugins, calls to load_plugin_textdomain cannot be made immediately. Plugins must call load_plugin_textdomain inside a function that runs on the ‘init’ hook, or at the earliest, the ‘plugins_loaded’ hook. Plugins that do not do this are coded incorrectly, according to advice from WordPress core developers. The fix for this is usually simply a matter of moving that single line of code to the correct place. If you find this problem affecting a plugin you are using, do your plugin author a favour and let them know (politely). Gengo will not change to accommodate broken plugins.
More on Gengo
- Gengo Download Page — Feature list and installation instructions
- Template Functions
- Frequently Asked Questions
- Gengo-related articles
If you want to help out and write/translate tutorials for Gengo:
Other Languages:
- Deutsch February 6, 2007
19 Responses
Comments:
Leave a Reply
You must be logged in to post a comment. Log in .
Trackbacks & Pingbacks:
-
Pingback from Fairweb » Blog Archive » Problèmes rencontrés avec le plugin multilingue Gengo
July 4th, 2007 at 8:08 am[…] problème provient d’une erreur du chargement de la localisation du plugin, dû à une incompatibilité avec d’autres plugins. Pour ma part, je l’ai rencontré lorsque j’ai utilisé Gengo avec Podpress qui permet […]
-
Pingback from Wordpress Plug-in: Problems activating PodPress while runnig Gengo — gemma+martin:blog
July 31st, 2007 at 9:15 am[…] Just one thing to be aware of is that Gengo grows deep roots in the WordPress system (because of the all-encompassing nature as a multi-language tool, which is, of course, not a problem because the guys have done a tremendous job in clean programming!) – that means, there may arise one or two conflicts with other plugins, which is documented here: http://wp-multilingual.net/download-gengo/compatibility/en/. […]
-
Pingback from Wordpress Plug-in: Probleme mit der Aktivierung von PodPress wenn Gengo installiert ist — gemma+martin:blog
August 1st, 2007 at 10:48 am[…] Eine Warnung zur Vorsicht aber möchte ich aussprechen: Gerade weil Gengo aufgrund seiner weitreichenden Natur der Sprachkontrolle tiefe Wurzeln im WordPress System schlägt kann es zu einstweiligen Konflikten bei der Installation von neuen Plugins geben. Keine Angst, die Jungs von Gengo haben klasse und saubere Programmierarbeit geleistet, und dicht an den WordPress Richtlinien für Plugins gearbeitet. Also, diese Problematik wird hier angesprochen: http://wp-multilingual.net/download-gengo/compatibility/en/. […]
-
Pingback from GaMerZ.WordPress » Blog Archive » Gengo Compatibility
September 18th, 2007 at 4:41 pm[…] hook, or at the earliest, the ‘plugins_loaded’ hook.” That is what being stated in Genko Compatibility Page. I have since updated all my plugins to solve that compatibility issue. Hopefully it will not break […]
April 5th, 2007 at 4:34 am
Compatibility with the gallery2 wordpress plugin can be fixed by editing the wp-content/plugins/wpg2/g2embed.php.
The first line of code which reads
load_plugin_textdomain('wpg2', 'wp-content/plugins/wpg2/locale');should be moved into the g2_init function. After making this change it has eliminated the get_currentuserinfo error when upgrading to Gengo 0.9
April 5th, 2007 at 4:37 am
Also discovered an issue with the gengo_next_posts_link. The function strrpos will only search for a single character in php4. I inserted the function from php manual entry for strrpos which will give the same functionality for php4 and php5.
April 7th, 2007 at 5:46 pm
Gengo doesn’t work with Wordtube 1.42.
Any way around that?
April 8th, 2007 at 12:51 am
Hi Oggg,
Looking at the Wordtube sourcecode, I can see that it is being localised incorrectly. It’s the same problem that also affected WP-ContactForm. The thread describing the problem and how Wordtube’s author can fix it is here.
April 10th, 2007 at 5:57 pm
The way to fix it in wordube is replacing
load_plugin_textdomain(’wpTube’,’wp-content/plugins/wordtube’);
for,
function wordTube_init ()
{
load_plugin_textdomain(’wpTube’,’wp-content/plugins/wordtube’);
}
add_action(’init’, ‘wordTube_init’);
May 29th, 2007 at 5:39 am
I’m having a hard time getting Gengo to work with the UltimateTagWarrior (UTW) plugin. Tags are a pretty important part of blogging, so it would be great if they could work with Gengo.
I think it is because the tag plugin expects the end of the URI to be the tag, but Gengo adds the language to the end of the URI. A solution would seem to be to change UTW so that it uses the word after /tag/ in the URI instead of the word at the end of it.
If anyone has had experience with the UTW plugin + Gengo and found a solution, I’d love to hear about it.
May 29th, 2007 at 7:37 am
Hi Brent,
I know this is a problem, but you should know that WordPress will natively support tagging in version 2.3. Gengo will of course support this by default. At the moment, I’m concentrating on other features and stability issues for WordPress 2.2. So, no, Gengo won’t work directly with UTW, but there will definitely be an importer from UTW to WordPress 2.3 native tagging, so you won’t be left out in the cold if you can wait that long.
Cheers,
Jamie.
June 9th, 2007 at 1:02 am
I’m trying to use genko and fulfill this dream of having my website/blog in english and portuguese..
problem is this plugin is I’ve been using wordpress more as a CMS than blog engine and I need it to search my pages, not only my posts.
So i use this plugin (as of wp 2.0) that simply does not work when genko is activated..
search pages 2.0
is the search query being overriden by genko?
(note: I still cant understand why searching pages isn’t a feature in wp)
July 20th, 2007 at 8:14 am
Hi
I have some compatibility problems with the GeoPress plugin. Has anybody else noticed that? Is there any solution?
Thanks for you help
L
July 27th, 2007 at 6:31 pm
Hello,
Did anyone find a solution to make wpg2 and Gengo work together?
tks
August 20th, 2007 at 5:36 pm
Hello,
It seems that WP-Postratings (v.1.11) is also incompatible with Gengo. Whenever I try to get both plugins to work together, I get this error :
Fatal error: Call to undefined function: get_currentuserinfo() in /mnt/145/sdb/9/9/nadglobtrotter/blog/wp-content/plugins/gengo/gengo.php on line 1080.I’ll write to the author of WP-postratings to ask for a fix, unless we can do something in Gengo (anybody)?
Thanks anyway for this AWESOME plugin!!!!
December 14th, 2007 at 4:20 am
Hi,
I found that Gengo also doesn’t work with the WP-Sticky -plugin
Does anyone know a way around that?
Thanks,
Piet
December 14th, 2007 at 4:22 am
Hi,
It seems that Gengo also doesn’t work with the WP-Sticky plugin (http://lesterchan.net/wordpress/readme/wp-sticky.html)
I get an error in line 1143 of gengo.php
Anyone knows a work-around?
Thanks,
Piet
December 14th, 2007 at 4:23 am
Hi,
It seems that Gengo also doesn’t work with the WP-Sticky plugin.
I get an error in line 1143 of gengo.php
Anyone knows a work-around?
Thanks,
Piet
December 14th, 2007 at 4:32 am
Apologies, it seems the latest version of WP-Sticky does indeed work with Gengo.
Also I didn’t realize that comments needed to be moderated first, that’s why you will see multiple comment attempts.
Thanks,
Piet