• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Awaiting feedback Pagination appears when there is no content to see. And empty pages for ignored content

Affected version
1.5.15

Alfa1

Well-known member
#1
I am not sure where to best post this as this is not a technical bug, and occurs in both XF1 and XF2.
When a filter is applied to results and there are no results, then you end up with an empty page with pagination.
The pagination links are basically dead links.

An example of this is when you are looking at a node that only has ignored content.
But it can also happen if there is no content in the node that you have permission to see.
Asides from this giving unexpected results, it also seems illogical that the user will see how many pages there are for content they have no rights to see.

A similar issue can be found when you ignore someone in the resource manager then you may encounter empty pages inbetween full pages or half filled pages.

it also affects XF addons in awkward ways.
 

Chris D

XenForo developer
Staff member
#2
In the context of ignored content, this is expected. We only hide the content on the client side. There are clearly drawbacks to this approach but it's also the most performant in that we don't have to do anything on the server side, which could lead to bigger problems.

Though you mention a few things here I'm not quite sure about, was this all related to ignored content?

When a filter is applied to results and there are no results, then you end up with an empty page with pagination.
The pagination links are basically dead links.
What kind of filter? What kind of results? The only thing we handle on the client side is the ignored content stuff. Other filters would be server side but in those cases we would calculate the number of entries and show pagination accordingly.

An example of this is when you are looking at a node that only has ignored content.
But it can also happen if there is no content in the node that you have permission to see.
Asides from this giving unexpected results, it also seems illogical that the user will see how many pages there are for content they have no rights to see.
Again, this isn't something we'd expect to happen. But in what context would you have a node where you don't have permission to view the content within it? Things like the view other's threads permission should be calculated correctly and only show pagination accordingly. Or are you talking about something where an add-on is involved?

Unfortunately this report is far too vague to really be able to comment on properly, other than the ignored stuff, which is expected. If you can provide some specifics and reproduction steps on the other stuff then we can comment further.