Sun 18 Mar 2007
Gengo 0.9 Reloaded
Posted by Jamie under Gengo.
A note explaining a slight modification to Gengo 0.9 and its rationale.
Or, re-uploaded at least. A small bug has been found and addressed in Gengo 0.9 that prevented users from translating side by side, due to a Javascript error. Rather than doing an entirely new release for such a small fix, I’ve just replaced the zipfile with the latest copy. Usually, this is considered bad practice, but the changes were made a very short time after the initial release and the problem is non-critical, so I decided that it would be fine in this case.
If you were one of the very early adopters of 0.9, you might find yourself affected by this bug, which is characterised by an endless spinning wheel when you click on the name of the post you are translating. If this is the case, re-downloading the Gengo package will fix the problem for you. Users of release candidates should also, of course, upgrade, if they haven’t already.
Thanks to Dzamir in the forum, who was quick to spot this problem and report it.
Other Languages:
- Deutsch March 18, 2007
2 Responses
Comments:
Leave a Reply
You must be logged in to post a comment. Log in .
March 19th, 2007 at 11:41 am
Hi,
I am trying to install it, but I got the following error at activation time:
WordPress database error: [BLOB/TEXT column ’summary’ can’t have a default value]
CREATE TABLE wp_summaries ( summary_id mediumint(6) NOT NULL auto_increment, summary_group mediumint(6) NOT NULL default ‘0′, language_id tinyint(3) NOT NULL default ‘0′, summary longtext NOT NULL default ”, PRIMARY KEY (summary_id) ) TYPE=MyISAM
WordPress database error: [BLOB/TEXT column ‘text’ can’t have a default value]
CREATE TABLE wp_synblocks ( block_name varchar(55) NOT NULL default ”, language_id tinyint(3) NOT NULL default ‘0′, text longtext NOT NULL default ”, PRIMARY KEY (block_name,language_id) ) TYPE=MyISAM
WordPress database error: [BLOB/TEXT column ‘description’ can’t have a default value]
CREATE TABLE wp_cat2syn ( cat_id bigint(20) NOT NULL default ‘0′, language_id tinyint(3) NOT NULL default ‘0′, synonym varchar(55) NOT NULL default ”, sanitised varchar(200) NOT NULL default ”, description longtext NOT NULL default ”, PRIMARY KEY (cat_id,language_id) ) TYPE=MyISAM
Any clue?
Did I miss something?
Thanks in advance,
Best regards.
March 19th, 2007 at 11:48 am
Hi, this problem has been raised in the forums and is as a result of running MySQL 5.0 in strict mode. You can find out some more and a temporary workaround here.