Some multi-page discussions in community will not show their first pages
I found this 2-page discussion via the Community search: Why have many records from the England and Wales Birth Registration Index suddenly disappeared? When I open it, the second page of the discussion is displayed. The navigation buttons at the top and bottom of the list both show that it is on page 2, but when I click the buttons for either the previous page («) or page 1, the second page is displayed again. I have seen this fault referred to in passing on 13 July in another unrelated discussion recently; it has 11 pages. The only way that I can see page 1 is by appending /p1 in the browser address bar to redisplay the page.
When I hover my mouse over the navigation buttons, the URL that is displayed in the pop-up at the bottom of the browser screen has just has the basic address of the discussion. It doesn't include the target page number (e.g. /p1). That basic URL will, as I understand it, always display the last page of the discussion. That is what is happening in the two examples I have cited.
Can Vanilla be changed so that the URLs for the previous («) and page 1 buttons are correct when their targets are page 1?
Answers
-
A Discussion I started in late 2025 ran to two pages. I wanted to make a copy for my files. Even from "My Discussions" only the second page will display.
Definitely a bug in the Community platform.3 -
Thank you for reporting this. You’re correct—when hovering over the navigation buttons, Vanilla currently displays only the base URL for the discussion. It does not include the target page number (such as
/p1) for the « or Page 1 buttons. Because the base URL always resolves to the last page of a discussion, the hover‑preview can be misleading, and I was able to replicate the behavior you described.This appears to be a limitation in how Vanilla generates and exposes navigation URLs. At this time, we don’t have a way to adjust that behavior on our end, but I’ve forwarded the issue for review to see whether the URL handling can be improved in a future update. I don’t have a timeline for any changes, but your report helps us document the problem and advocate for a fix.
Thank you for bringing this to our attention and for helping make the FamilySearch Community experience better for everyone.
1 -
A fix for this has been applied and it should be fixed. Let us know if you have any further issues. Thank you for the feedback!
3 -
Thank you @Tomlinsonkl
0
