New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: Add a setting to make all content fieldsets localizable #1220

Closed
peimn opened this Issue Feb 1, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@peimn

peimn commented Feb 1, 2017

Expected behaviour

When I made my site multi language and localized I am expected the content fieldsets must be localizable

Actual behaviour

In any of the fieldsets that we want to be multilingual we have to set it localizable, but in pages that no have specific fieldset (like home page in default installation of Statamic) the content is not localizable until you make a fieldset for it and define it localizable there is also a bug of doing this way, I'll post it as another issue

It may be useful to have a global settings to make all content localizable.

Edit:

I posted mentioned issue: #1221

@peimn

This comment has been minimized.

peimn commented Feb 1, 2017

I have realized that the pages that don't have fieldset in their content, use default fieldset but the default fieldset is not included with default installation bundle of Statamic

@jasonvarga

This comment has been minimized.

Member

jasonvarga commented Feb 1, 2017

Create a default.yaml fieldset to override the default, which is just a single, lonely, unlocalizable content field.

@jasonvarga

This comment has been minimized.

Member

jasonvarga commented Feb 1, 2017

We'll make sure to document this better, and/or make the fields localizable out of the box. It was an easy thing to miss!

@ebeauchamps

This comment has been minimized.

ebeauchamps commented Feb 1, 2017

Similar to a FR already opened regarding a way to localized the display: part of a field in a fieldset
#1014

@jasonvarga

This comment has been minimized.

Member

jasonvarga commented Feb 1, 2017

I've made the content field in the default fieldset localizable for next release so it works better out of the box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment