Skip to:
Content

bbPress.org

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#2762 closed defect (bug) (duplicate)

Sticky posts generate off-by-one pagination count error on page 1

Reported by: mechter's profile mechter Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.5.4
Component: Component - Topics Keywords:
Cc:

Description

Recreation:

in the settings, limit number of posts per page to 3
add 6 topics
go to page 1 of forum
note that there are 2 pages as expected
go to page 2
edit one of the posts and make it sticky
go to page 1
note there are now 3 pages where 2 would be expectedd
clicking on page 3 will show "no topics found" message
go back
click on page 2
note that on page 2 the number of pages is 2 as the error only seems to occur on page 1

(WordPress version used to test is 4.1.1)

Change History (5)

#1 @netweb
11 years ago

  • Component changed from General to Component - Topics
  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate: #1642

Thanks mechter, please see the above ticket.

#2 @mechter
11 years ago

Yep, just found it via the search.. I've noticed that ticket 1642 is three years old and there was talk about moving a fix up to 2.2.. I guess this bug will never be fixed then.

#3 @netweb
11 years ago

As John wrote:

I'm bumping this to 2.2. Agree this is annoying, but it's edge case and not a trivial fix.

The above still stands true and as such it is a matter of what limited time we have available and to determine what is the best use of that time.

Any contributions in helping us out to patch and fix outstanding issues are of course always greatly appreciated. :)

#4 follow-up: @mechter
11 years ago

I know what it's like. If it's not trivial for someone familiar with the code base, I don't think I'll touch it any time soon. If I get around to it and do find a fix, however, I'll make sure to post it here.

#5 in reply to: ↑ 4 @netweb
11 years ago

Replying to mechter:

I know what it's like. If it's not trivial for someone familiar with the code base, I don't think I'll touch it any time soon. If I get around to it and do find a fix, however, I'll make sure to post it here.

Thanks, if you do find yourself peeking at the code and come up with a fix add that would be cool, but add the details to the #1642 ticket please ;)

Note: See TracTickets for help on using tickets.