how to create named anchors in django for getting down to specific parts of the page

Question

I'm creating a "Q & A" website. On the questions page all of its answers could be seen (with pagination). I need to go straight down to answers (in the page) from other pages as well. I've tried implementing named anchors but unable to direct to page section.

Answer's get_absolute_url() returns url in the form:

www.example.com/question-id/question-slug?page=no#aID <!-- EDITED -->

An example url:

www.example.com/question-10/what-is-this?page=2#a20   <!-- EDITED -->

and in html:

    {% autopaginate answers 10 %}
    {% for answer in answers %}
      <div>
        <a name="a{{answer.id}}">Answer</a> <!-- EDITED -->
        {# answer body goes here#}
      </div>
    {% endfor %}
    {% paginate %}

It redirects to the correct page but not to the correct page section.

EDIT: Result! When clicked, After going to the page section, it bounces to the bottom of the page

Answer 1

a_{{answer.is}}

may be you have a typo - iD ?

a_{{answer.id}}

Answer 2

A surprisingly little-known fact is that anchors can go to any element with an ID on the page; it doesn't have to be an anchor element. So you might just put the ID on your div:

<div id="a_{{answer.id}}">
    <span>Answer</span>
    {# answer body goes here#}
</div>

(Obviously, use whatever element makes sense around the answer header; the span above is just for illustration.)

As far as I know, there's nothing wrong with using anchors (although anchors with content tend to exhibit link-like behaviors -- rollovers and such -- if you're not careful with your CSS), but just as an option, you have this other alternative as well.

Answer 3

http://www.example.com/question-10/what-is-this#a_20/?page=2
<a id="a_{{answer.id}}">Answer</a>

There is no mechanism of path parts (/) or query strings (?) in a fragment identifier.

Is the pagination parameter supposed to be sent to the server-side? If so, that's an easy fix:

http://www.example.com/question-10/what-is-this?page=2#a_20

If not; if you're doing client-side pagination, which is why the query was appended as part of the fragment identifier, then you've got trouble.

You can't link to part of a document and include extra parameters for client-side-scripted pagination: you can have a fragment identifier that points to a real identified element on the page, or a fragment identifier being used as a hack to pass parameters to script, but you can't have both at once. The fragment you have specified is a single long string, and can only be matched by:

<a name="a_20/?page=2">foo</a>

(I used the old-fashioned name attribute here instead of the usually-preferred id attribute because this:

<div id="a_20/?page=2">foo</div>

is invalid. id attributes cannot include arbitrary punctuation characters; they are NAME tokens which may only be alphanumerics, _, ., - and : (though the latter is inadvisable). If you wanted to specify other types of character they would have to be encoded in some application-specific way.)