Hi, the problem is most probably the fact that the Blog application doesn’t use the page title and content to store the blog post title and content. It uses instead object properties. There’s a BlostPostClass object attached to the blog post page that holds the blog post title and content. And objects are not translatable ATM. They are shared by all page translations. See:
We are on 15.10 and it looks like blog translations now save. We can select ‘translate this page’, create the translated version, and see an option in the drawer menu to toggle between the translated versions by selecting language.
I’m reporting back to say we realized that the reason it looked like we could translate our blogposts was because we had selected the ‘Create’ button that results in a page, not a blogpost.
It’s a bit confusing (and I am sure it will be for our future users as well) that there are two ‘create’ buttons for the blog application; one of which creates a page (translatable), and one that creates a blog post (not translatable). Is there a way to make this distinction more clear? I expect that for users who are used to creating pages from the main +Create button, they may default to selecting that button over the Blog create button further down on the page.
