Forum posts to 'Archive'

Re: Translatable Fatal error

fdqepd — Wed, 27 Aug 2008 00:25:23 +1200

hello, any news on this subject?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

crazyScripter — Sat, 12 Jul 2008 03:24:22 +1200

I'm interesting in resolving this problem too, probably this is already fixed in some branch in SVN, so I can checkout latest version... Please advice, or I'll have to fix this by myself.
Thanks in advance.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

YellowDuck — Tue, 08 Jul 2008 19:05:07 +1200

Any update on this? I've stumbled across the exact same problem and I'm in desperate need to get a fix for this...

I'm running SilverStripe 2.2.2 and the problem is still the same.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

pIscIs — Tue, 10 Jun 2008 01:32:37 +1200

so is where any avalaible branch with this bug fixed?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Ingo — Wed, 12 Mar 2008 21:54:54 +1300

not that i'm aware of, sorry mate

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Fuzz10 — Wed, 12 Mar 2008 21:42:25 +1300

Thanks Ingo...

Just to be sure ; there is no (quick,dirty) way to use the I8N functionality for pages that have custom fields , correct ?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Ingo — Wed, 12 Mar 2008 09:27:05 +1300

no news yet, make sure to follow the progress of these tickets:
http://open.silverstripe.com/ticket/2202
http://open.silverstripe.com/ticket/2165

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Fuzz10 — Wed, 12 Mar 2008 02:47:21 +1300

Is there any news on the translations of custom fields ?
Anyone had any succes with the i8n functionality in a production environment ?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Craneway — Sat, 23 Feb 2008 10:51:52 +1300

I tried to do the same but was not lucky. My site has just several pages with the same sidebar content in custom areas. So, I did a trick creating separate pages with the needed content for custom blocks and called that content from those blocks in the template.
This is not a perfect solution, but I'll wait until the patch is released and custom fields that we create for the cms become fully translatable.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Nimolix — Sat, 23 Feb 2008 08:47:21 +1300

I've encountered the same problem; I want to make some custom fields translatable.
I'm working on a web project using SS and today when I wanted to implement custome field functionality, It gave me 'can not run query' error and referred to non existing column in SiteTree table named OriginalLangID.
As I should deliver my project next week, I would appreciate to access the patch early. I was thinking about extending $db static variable in SiteTree class and add all of custom fields and then selectively disable them in each page type I've created. Although it is non-efficient but quick fix that I think functional.
I've not tried daily builds yet, Do u think if I upgrade my local copy with latest daily build files, my problem is solved?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

yitter — Fri, 08 Feb 2008 10:54:15 +1300

that sounds very good, can't wait to see that fix working!
Thats for the great work btw.

cheers

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Ingo — Fri, 08 Feb 2008 09:31:58 +1300

we've got a fix in one of our project branches, which matt will merge back to trunk soon (~Â 2 weeks). basically we're defining translatable-fields on a new static in the SiteTree class instead, and have cleaned up the DataObjectDecorator logic a bit.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

yitter — Fri, 08 Feb 2008 01:51:15 +1300

well messing with the translation system also got me into trouble. You mentioned to re-set all extensions in the Page class, I did it like that:

class Page extends SiteTree {
...
/* this is just copied from SiteTree*/
static $extensions = array(
      "Hierarchy",
      "Translatable('Title', 'MenuTitle', 'Content', 'URLSegment', 'MetaTitle', 'MetaDescription', 'MetaKeywords', 'Status', 'ExtraMeta')",
      "Versioned('Stage', 'Live')"
   );
...
}

I'm not sure if this is a real re-set but the problem is still the same: Adding Custom Fields to the Translateable causes serious errors. But when doing the same in the Site Tree Class (new Custom field etc.) I can add it to the $extensions Translateable array .... Strange enough?!

But if I now try to Translate a Page only the original Site Tree Fields can be translated, the new Field is only viewable (not editable) and I can't find any reason why that is. It is strange ...

Any suggestions?

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Ingo — Mon, 28 Jan 2008 07:50:13 +1300

fair enough, thanks for your patience. we're just bulding our first commercial applications with the translation system as well (it was built by a google summer of code student), so its still a fairly young component of Silverstripe.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

hitautodestruct — Mon, 28 Jan 2008 01:55:25 +1300

Hey Ingo
Thanks for the reply but I have gone about a different way of setting up translating my site.
I now have a duplicated HomePage and Page page types with a different language prefix for each language.
Example:
german is de-home,
spanish is: es-home etc.

This is also more SEO compatible since the search engine does not recognize the ?lang= attribute and can't index the other language pages.

I have messed around way to much with the translation system and all it did was cause me trouble. So, I'm not going to test out anything else.

But on the plus side I'm still using SS for the purpose I initially intended it for, which is a multi-language site.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

Ingo — Sat, 26 Jan 2008 18:34:45 +1300

hm this might be a bug in the translation system - can you try re-setting all $extensions in your subclass? see sapphire/core/model/SiteTree.php $extensions array.

Posted to: Translatable Fatal error Show Thread | Post Reply

Re: Translatable Fatal error

yitter — Mon, 21 Jan 2008 14:49:34 +1300

Just wanted to say, I have the exact same problem. Anyone has suggestions on how to solve this? Is it a Bug?

Posted to: Translatable Fatal error Show Thread | Post Reply

Translatable Fatal error

hitautodestruct — Wed, 09 Jan 2008 01:08:44 +1300

Hey there anyone that can help.

I have managed to get my site up and running with custom fields and templates.
So now the only thing thats stopping me from implementing my Silverstripe site and the main reason for choosing this framework is the Translatable option.

It seems that every time I enable the:

static $extensions = array("Translatable('CustomField')");

For one or many of my custom fields I get a dramatic Fatal Error.

I have tried everything to no avail.
Can anyone help me with this?

SilverStripe ver. 2.2.1
Apache, MySQL and PHP5
Are all according to stats.

This is the code for my HomePage.php Pagetype:

<?php
class HomePage extends SiteTree {
   static $db = array(
      'Slogan' => 'Varchar'
   );

//This is the code I insert that causes all the problems
   static $extensions = array(
      "Translatable('Slogan')"
   );

static $has_one = array(
);

static $defaults = array(
);

function getCMSFields() {
$fields = parent::getCMSFields();

$fields->addFieldToTab('Root.Content.Main', new TextField('Slogan', 'The slogan text under the rummy royal logo:'), 'Content');

return $fields;
}
}

class HomePage_Controller extends ContentController {
   function init() {
      parent::init();
      Requirements::themedCSS("RummyStyle");
   }
}
?>

I attached the error page to this post as well.

Posted to: Translatable Fatal error Show Thread | Post Reply