id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
13344	"Name collision for ""next"" template variable between contrib.comments and views.generic.list_detail"	Erik Stein	nobody	"Both the comment system (in `post_comment` and it's accompagnying forms) and the generic views system (in `views.generic.list_detail`'s legacy template context stuff) use a template variabled named ""next"". The comment app's templates `approve.html`, `delete.html`, `flag.html` and `preview.html` render a hidden form field if `next` is not empty.

If you use for example the `list_detail` view with a template which renders a comment form for each list item, the comment form wrongly uses the `next`-value from the `list_details` view (the next page number). On posting the comment the user get's an 404 error, because the `post_comment` view now tries to redirect to a wrong URL containing the next page number.

Maybe it's generally a bad idea to use very simple context variable names like `next` in prepackaged apps."	Bug	closed	contrib.comments	1.2-beta	Normal	wontfix			Design decision needed	0	0	0	0	0	0