hi,

playing arround with the SS3 translateable module from github ... I can't create new translations for pages.
on the "translations" tab is the button "create". but nothing happens if I click the button.

and if I want switch the language (in backend, above sitetree) this message appears:

The action 'LangForm' does not exist in class CMSPagesController

I think SS3 would'nd be the best choise for a new multilanguage site?

any ideas?

I think SS3 would'nd be the best choise for a new multilanguage site?

SS3 is not ideal for ANY site until it is stable and required modules are stable

any ideas?

raise a bug on open.silverstripe.org

Ingo has just moved all the tickets for translatable to the modules github page. It requires a developer to take a look at it for 3.0 compatibility (like most modules!).

hello,
i was thinking to create a new website with ss3 rc2.
multi language will be one of the main features of the site.

do you recommend to wait then for the final release?
also it might be hard with missing documentation.
many things might have changed right?

thx and greetz,
florian

Hello. This issue still doesn't seem to be fixed 3 months later. Translable 1.0.0-30 is not working at all with SilverStripe-cms-v3.0.2. The issues I experience consist of the following:

1. In admin/pages/?locale=en_US, after selecting different language and pressing GO I receive the message "The action 'LangForm' does not exist in class CMSPagesController"
2. Create button doesn't work at all, when trying to create new translation in Translation tab.

Am I doing something wrong? SilverStripe looks good for my future projects but i18n is crucial for all of it. Should I wait, code/configure or leave disappointed?

You have two options...

1) use 2.4.7 which has translatable out of the box and is fully documented etc. <-- my choice/recomendation
2) fix some of the https://github.com/silverstripe/silverstripe-translatable/issues with the "new" module.
3) leave disappointed

Personally I feel this is a pretty poor show from silverstipe to take away core functionality like this and then leave it unmaintained for months. But then it is all free and the developer can fix it. this and several more issues are why I have not moved to SS3 yet the "cost" of this new "free" version is not low enough yet.

I choose swaiba's option 1 and add an option 4) Stay disappointed until it's fixed.

Hopefully someone will take it onboard. If not, without a working Translateable module, or an affordable other option, there'll never be an upgrade happening here.

Just out of curiosity, is there any progress on making the module compatible for SS 3.0?