Multi-language integration, issue with children pages not translating

[fabie]

Hello,
My name is Fabienne and I am the principal consultant of
UntangleMyWeb.com. I recommend SilverStripe to my clients and have
currently been working with a few projects in my home country
(Swtizerland, but now live in AUS) and really enjoy i18n. I have been
working with Tate who I contract to develop the sites using
SilverStripeand I manage the projects. I have an IT background but
zero knowledge of PHP.

Recently, we had the latest release of SilverStripe with i18n but we
experienced too many bugs to go ahead so we reported them and reverted
to r 2.2.2. However, we are now experiencing an issue with the
Children not wanting to translate.

We have lodged a bug #2526 but I was hoping to get insight on a few
others who might have found a way to bypass this issue in the
meantime. MattSS and DesignCity have already helped immensely but I
would be keen to know if others have also found a solution or a
workaroud.

I would also love to see other multi-language sites implemented with
i18n and SilverStripe!

Thanks in advance for your response

Fabie

[Matt Peel]

I was talking to fabie about this on IRC, and I had the same problem
with a recent site. The reason for the problem is sort of a catch-22 -
you can't translate the page because you can't see, because it doesn't
have a translated version yet. The current code breaks this rule for
root-level pages (those with ParentID = 0) so that the first level
always appears, but doesn't seem to have any children. The workaround
right now is to switch to the default language, find the page you want
to translate (e.g. a second-level page), then create a new translation
from the dropdown under the Translations tab. Once you've created the
translation and saved it, the next refresh of that tree should show the
child page when in the translating language.

Ingo and I had a crack at fixing it a while back, but time was tight on
the project and it was the day before launch, so we ended up not quite
polishing it off, I might try and dig out the code and patch the latest
2.2.2 if I have some spare time.

Hopefully that at least helps as a workaround until the issue is patched.

Matt.

[fabie]

Thanks Matt for all your help, I was meant to inform the Group but you
beat me to it!