-
Notifications
You must be signed in to change notification settings - Fork 119
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
Blocks support? #82
Comments
If you use the latest alpha release (v0.5.0a1) it doesn't need the mixin, and in theory it's just based on modeltranslation so it should work on StructBlock type models (but it doesn't). I'd been meaning to point out the same issue, registering the StructBlock model with modeltranslation seems to fail. |
If I may resurrect an old issue ... we've installed 0.8 with Django 1.11.10 and wagtail 1.13.1 (all the latest, I think) and are encountering the same limitation. Trying to register a I don't mind working on the code and submitting a PR if I could maybe get a pointer to start. |
Hi @Jason-Abbott! All contributions are welcomed. I'm not aware of what kind of subtleties |
Thanks @dmarcelino. I've started working on this. The Wagtail blocks are quite a bit different from the pages and panels since they aren't Django models so I'm approaching from another angle. I'll share when I have something. |
Hello @Jason-Abbott Cheers |
Has anyone attempted this yet? I may be giving it a whirl. |
@mihow did you attempt to fix the translation for Struckblocks? |
Hello,
Can this package work for Block translations?
Assuming we have a block such as the following one:
Would it be possible to enable translations on its fields?
Applying the TranslationMixin doesn't work.
I guess it was made to only translate Pages or Snippets.
The text was updated successfully, but these errors were encountered: