You MUST use this template when reporting issues. Please make sure you follow the checklist and fill in all of the information sections below.
All versions of django-smart-selects prior to version 1.2.8 are vulnerable to an XSS attack as detailed in issue 171. As a result, all previous versions have been removed from PyPI to prevent users from installing insecure versions. All users are urged to upgrade as soon as possible.
Checklist
Put an x in the bracket when you have completed each task, like this: [x]
[ x] This issue is not about installing previous versions of django-smart-selects older than 1.2.8. I understand that previous versions are insecure and will not receive any support whatsoever.
[ x ] I have verified that that issue exists against the master branch of django-smart-selects.
[ x ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
[ ] I have debugged the issue to the smart_selects app.
[ x ] I have reduced the issue to the simplest possible case.
[ ] I have included all relevant sections of models.py, forms.py, and views.py with problems.
it's would be really good if I could have a model using more than one field. I don't know how exactly this might be done. Maybe creating something like MultipleChainedForeignKey. Something like that:
You MUST use this template when reporting issues. Please make sure you follow the checklist and fill in all of the information sections below.
All versions of django-smart-selects prior to version 1.2.8 are vulnerable to an XSS attack as detailed in issue 171. As a result, all previous versions have been removed from PyPI to prevent users from installing insecure versions. All users are urged to upgrade as soon as possible.
Checklist
Put an
x
in the bracket when you have completed each task, like this:[x]
master
branch of django-smart-selects.smart_selects
app.models.py
,forms.py
, andviews.py
with problems.Steps to reproduce
Actual behavior
The ChainedForeignKey allows chained just one field on the model referenced. I've already use this feature like that:
Expected behavior
it's would be really good if I could have a model using more than one field. I don't know how exactly this might be done. Maybe creating something like MultipleChainedForeignKey. Something like that: