Skip to content
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

TranslatedField issues #67

Closed
mchccc opened this issue Mar 27, 2015 · 2 comments
Closed

TranslatedField issues #67

mchccc opened this issue Mar 27, 2015 · 2 comments

Comments

@mchccc
Copy link
Contributor

mchccc commented Mar 27, 2015

I think that on row 138 of file forms.py the last parameter is meant to be **attrs[f_name].kwargs instead of **translated_fields[f_name].kwargs.

Besides that, I'm having issues getting the field rendered: I'd like to use a CKEditor widget, and that does not seem to work, but even if I remove the custom widget setting the label is rendered as %(contents)s: instead of simply contents.

edit: the label thing was totally a (stupid) error on my side, but I still can't get the custom widget to work.

Is there any way I could fix this?

edit: well disregard all of that, I am a tool.

Thanks

@mchccc
Copy link
Contributor Author

mchccc commented Apr 1, 2015

Issued a pull request to fix the wrong variable name;
I'd suggest merging it (or anyway fixing the small typo) as soon as possible, since it throws an exception immediately when building forms with custom widgets.

@vdboor
Copy link
Contributor

vdboor commented Apr 9, 2015

I've merged #68 - can you confirm this is now correct? And if you can, please provide a unit test for this feature.

@vdboor vdboor closed this as completed Jun 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants