8.1.1: comment link uses first cached page of comments;
links to comments on other pages then refer to wrong page.
Repeatable: always
OS: Ubuntu 14.04.4 LTS
PHP: 5.5.9+dfsg-1ubuntu4.16
Msysl: 5.5.49-0ubuntu0.14.04.1
Prepare test:
- Install standard, english 8.1.1.
- As admin, create 1 article (node/1)
- Create 15 comments with title C1, .., C15 for the article
- In article content type, modify comments field to show 10 (not 50) comments per page
- For reproducing, use two tabs:
- - E) Effect: one for filling the cache and checking the effect of that
- - C) Cache: one for clearing cache (administration, configuration, performance, button clear cache)
How to reproduce, Actual Results:
Case 1:
- E) goto home page
- C) clear cache
- E) click article link
- E) navigate to page 2 of the comments using pager
- E) click permalink of a comment, say C13 (you created 15 comments)
*1E) /comment/13 is "displayed": the first page of comments (with C3) is displayed (C13 is on page 2)
Case 2 (variation)
- E) goto home page
- E) click article link
- E) navigate to page 2 of the comments
- C) clear cache
- E) refresh page (with page=1 in the url, the second page of comments)
- E) navigate back to page 0 of the comments using the pager
- E) click on any comment title, say C3
*2E) C3 is shown (as expected)
Case 3 (variation)
- E) goto home page
- C) clear cache
- E) display e.g. (yourdomain)/comment/13 (directly via browser address toolbar)
- E) C13 is displayed (as expected: first user is lucky!)
- E) go back to page 0 using pager
- E) Click on C3 (title)
*3E) page 1 of the comments is shown (C13 is visible, not C3)
Expected results (see inline in Actal results too)
*1E) show page 1 with C13
*2E) show page: this is ok. Accessing the page via pager seems to be different.
*3E) show page 0, with C3 visible
Note: you can also use permalinks instead: this is how I discovered it, see below.
--
Analysis: as an attempt of interpretation
(of a newbie: I just went live with my 8.1.1 from migrated Ning2 because of emergency):
a) referencing comments directly in the cache system seems to set the page
which is used for subsequent
b) referencing the page via pager does not seem to set the cache mentioned in a)
--
Motivation:
I discovered this via the migrated link directories I have in my migrated site:
users click, and they do not get to the collected content comment,
but to the content page of the comment the first user after cache clear clicked.
Since I have big threads and 1500 internal links, this matters for me.
--
This is my first issue: please have mercy if I made any mistakes for doing so ..
(I will publish my migration (like the one for D7) in GPL,
and I am grateful to drupal community, yet I know very little, at least not yet).
