Error with rules on CreateView introduced in 1.4
See original GitHub issuehttps://github.com/dfunckt/django-rules/blob/master/rules/contrib/views.py#L37
Using self.get_object
will introduce an error when using rules
on a view that inherits from CreateView
. This is because CreateView
does inherit SingleObjectMixin
and does have a get_object
callable, but it will throw an exception when its get_object
is called:
AttributeError: Generic detail view {InheritsFromCreateView} must be called with either an object pk or a slug.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Solved: Hive CREATE VIEW fails due to no SELECT access on
I have been validating the Ranger options. I have select on all columns of a hive table: SELECT ssn, name, location FROM employee;....
Read more >527364 – inconsistentName error for the oid with the number ...
Reason: inconsistentName (That object can not currently be created) Failed object: SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStatus."vmini".8.1.3.6.1.4.1.2021.
Read more >[Snackbar] InflateException thrown on obfuscated builds #1814
I can work on reproducing this on my end and see what's happening. Have you explored any proguard keep rules with any success?...
Read more >Errors -206 and -111 attempting to access database objects ...
Cause. Errors -206 and -111 indicate the object does not exist in the remote target. To construct the fully qualified name, the following...
Read more >django createview, how to reset the initial value in the form?
i got a "list indices must be integers, not str" error, i've checked the source code, the possible method i need to rewrite...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think the solution should be in
django-rules
@dfunckt Any chance of a new release with this fix pulled in?