#16579: An issue of migrate comments to databrowse.
-------------------------------------+-------------------------------------
Reporter: leopku | Owner: nobody
<leo.ss.pku@…> | Status: closed
Type: New | Component: contrib.databrowse
feature | Severity: Normal
Milestone: | Keywords: databrowse,
Version: 1.3 | comments
Resolution: invalid | Has patch: 0
Triage Stage: | Needs tests: 0
Unreviewed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Indeed, this happens because databrowse hands a wrapper (!EasyInstance) to
the view, not the original object. Try this: `{% render_comment_list for
object.instance %}`.
I'm not sure if this qualifies as a bug: databrowse's documentation
doesn't describe the templates, and databrowse is intended as a
plug'n'play tool, not as a basis for further development. Also, I don't
know how we could "fix" this: !EasyInstance is really a core component of
databrowse.
For these reasons, I'm marking this ticket as invalid. However, if you
have an idea to improve Django with regard to this problem, please reopen
the ticket and describe it.
--
Ticket URL: <https://code.djangoproject.com/ticket/16579#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
