-
Notifications
You must be signed in to change notification settings - Fork 1
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
Make fields in User localizable for front-end #1256
Comments
Unlike entries or terms, users can't be localized across sites. The "localizable" icon shouldn't be showing on user blueprints. |
Alright, got it! But, wouldn't it be a good thing to have? Although I can't come up with another suggestion than my own above, having localized fields for users. 🤔
Yes, that was also one thing i was wondering about. If it's not possible to have it localized we shouldn't show it for the user. 👍🏻 |
The easiest way to "localize" users right now would be to have separate fields for the various locales. We can keep this feature request open.
Yep, they shouldn't be showing. I've opened a bug report for that: statamic/cms#11048 |
Hello there!
I've created a new field called "bio" where the user can tell a bit about them self, then i'm using this in the articles page.
This is a multisite with two languages. I've localized the "bio" field, but somehow when i switch between site in the control panel i only see one translation. This also reflects in the front-end, i can't see the English translation when i switch to that page.
Is this something that others would find good to have? Or is there a good workaround on this?
Adding some images for better clarity.
Here i could just display some biography on the person who wrote the article based on the locale.
The text was updated successfully, but these errors were encountered: