Thank you for the help @crhodes. I don't understand how you mean to pass in this url to the view. How else to do it, except via its line in urls.py? This is how the documentation says to pass in the template_name parameter to the views.login() function (as in the source code you linked to): (r'^accounts/login/$', 'django.contrib.auth.views.login', {'template_name': 'myapp/login.html'}),. Since another parameter in that same function is redirect_field_name, I thought using the same method of passing would work, but obviously it doesn't. Can you please elaborate on what your suggesting?

谢谢你的帮助@crhodes。我不明白您的意思是如何将此url传递给视图。除了通过urls.py中的代码行之外，还能怎么做呢？文档介绍了如何将TEMPLATE_NAME参数传递给views.login()函数(与您链接的源代码中一样)：(r‘^ACCOUNTS/LOGIN/$’，‘django.contri.auth.views.login’，{‘TEMPLATE_NAME’：‘myapp/login.html’})，。由于同一函数中另一个参数是REDIRECT_FIELD_NAME，我认为使用相同的传递方法会起作用，但显然不起作用。您能详细说明您的建议吗？

From what I understand there are two options, either you specify the url in the querystring like so: ?next=/albums/all/. Or, you specify a redirect_field_name and customize the login template as the docs note: Note that if you provide a value to redirect_field_name, you will most likely need to customize your login template as well, since the template context variable which stores the redirect path will use the value of redirect_field_name as its key rather than "next"

据我所知，有两种选择，要么你在查询字符串中指定URL，就像这样：？下一个=/albums/all/.或者，您指定一个redirect_field_name并自定义登录模板，如文档注释所示：请注意，如果您为redirect_field_name提供一个值，则很可能还需要自定义登录模板，因为存储重定向路径的模板上下文变量将使用redirect_field_name的值作为其键，而不是“next”。

I understand the manually adding ?next=... to the url. I don't know how to "specify a redirect_field_name" As far as customizing the template, I can only guess that it means changing <input type="hidden" name="next" value="{{ name }}" /> to ...name="next" value="{{ redirect_field_name }}" />. If you would be willing to continue this in chat, it would be helpful.

我理解手动添加？NEXT=...发送到URL。我不知道如何“指定REDIRECT_FIELD_NAME”就定制模板而言，我只能猜测这意味着将更改为...NEXT“VALUE=”{{REDIRECT_FIELD_NAME}}“/>。如果你愿意在聊天中继续这个话题，那将是很有帮助的。

If you change the redirect_field_name the template would change as you suggested. However I believe it would be input type="hidden" name="{{ redirect_field_name }}" value="/albums/all/" />. If you look at the source I linked the redirect_to variable storing the url is first checked for in the POST to see if the redirect_field_name is there, otherwise it falls back on the GET and the url being in the querystring.

如果更改REDIRECT_FIELD_NAME，模板将按照您的建议进行更改。然而，我相信它将是输入type=“隐藏”名称=“{{REDIRECT_FIELD_NAME}}”值=“/albumes/all/”/>。如果您查看我链接的reDirect_to变量的源代码，那么首先在POST中检查url，以查看reDirect_field_name是否在那里，否则它将依赖于GET和查询字符串中的url。

Oh! It's a name. I don't care about the name! I want the value to be /albums/all/. Right? Well that certainly clears things up a bit. So I could just forget about this redirect_field_name variable entirely, and just hard-code the value right into the template. That doesn't seem like "the right way" to do it, but it's a step in the right direction. (I wrote name="next" value="{{ name }}"/> in my previous comment, should be value="{{ next }}"). Let me give it a try!

噢!这是个名字。我不在乎名字！我希望该值为/albots/all/。对吗？好吧，这肯定会让事情变得更清晰一些。因此，我可以完全忘记REDIRECT_FIELD_NAME变量，并将值硬编码到模板中。这似乎不是“正确的方式”，但这是朝着正确方向迈出的一步。(我在前面的评论中写了name=“Next”Value=“{{name}}”/>，应该是Value=“{{Next}}”)。让我试一试吧！