Please guys, we've said it often enough: don't use Translatable in 2.3 yet.
It would be much more productive if you help us test the new Translatable datamodel on trunk,
so we can ensure a stable release of this very soon.
Lars, I'd be particularly interested in your findings with running Translatable (on trunk) with a different default language.
it's amazing to develop a new version which is not compatible with this main functionnality :(
we can use now serious admin generator but the application can resolve the translation of my website !!! and now I must change technology for my project
@Blanchon : I understand your frustration , but the core-team was pretty clear on that matter; they did not force you to upgrade to 2.3.0.
@Ingo : Agreed , but I can't even properly run a site with Dutch text ; Silverstripe produces the wrong meta-information for the site. In search for a quick hack for that. ;-) I'll make sure to try out the trunk over the next couple of days.
@Fuzz10: by the wrong metadata do you mean <meta http-equiv="Content-Language" content="nl-NL"> ? My Dutch site is OK in 2.3.0 just by setting i18n::set_locale('nl_NL'), but only after applying the R72367 changes. That besides the translatable issue, for which I'm waiting patiently :-)