problem with pagination

[Ty]

Forum URL: crosswire.boards.net

Alright so while entering a thread normally, through a board, the pagination links and navigation works fine.

However, when I click on the link to a thread in the Participated pop-up window and it takes you to the page (not the first page) in which the new post is on (such as the second page in a thread) the pagination links no longer work. 

It just refreshes the current page.  When I click on the pagination to get to the first page, while on the second page, the address bar will at first show the "?page=1" to show that I have indeed clicked it, but instead it just refreshes and puts that "?page=2" back in there.  It however does not change the "page/2/" portion of the url, which is why it probably remains on the same page..thus making it impossible for me to visit a previous page when I visit a thread through the participated feature.

[Craig]

Ah. This may explain the error that some people have been getting, but hasn't been linked to the participated threads link. I have marked this as attention to the development team who will look into it and fix it

Thanks.

Craig

[CheatAreZee]

I'll tag a few devs just to ensure that this will be seen

Keith Rozett, Vinh, Tim Camara

[Vinh]

Hi Ty,

I believe it is one of the plugins that is causing the issue because when I run your forum with plugins disabled, it works fine. If you need help with identifying which one it is, I can help as long as you don't mind me disabling some plugins for a few minutes while I try to figure it out.

[Ty]

May 1, 2013 9:30:47 GMT -8 Vinh said:

Hi Ty,

I believe it is one of the plugins that is causing the issue because when I run your forum with plugins disabled, it works fine. If you need help with identifying which one it is, I can help as long as you don't mind me disabling some plugins for a few minutes while I try to figure it out.

I just went through the process of disabling and testing them one by one myself...and it is indeed the Awards System plugin.

[Vinh]

Great, you may want to report the bug to the Plugin author or in the thread if you haven't already.

[Chris]

May 1, 2013 9:30:47 GMT -8 Vinh said:

Hi Ty,

I believe it is one of the plugins that is causing the issue because when I run your forum with plugins disabled, it works fine. If you need help with identifying which one it is, I can help as long as you don't mind me disabling some plugins for a few minutes while I try to figure it out.

Vinh until some official guidance is given or an official pagination callback interface is offered these errors that affect forum functionality will continue to occur. As an example here is a case where there was an error in the handler of a plugin hooking the aftersearch event which led to the symptoms described in this thread.

Apr 10, 2013 18:08:19 GMT -8 Chris said:

I took a quick look at this ...
Although there's a qualifier to ignore .guest-mini-profile, there's nothing preventing processing of Camille's profile which has no user-link [class] (deleted member perhaps Army?). This causes an error which eventually redounds on pagination since pagination is disabled in beforeSearch then re-enabled in afterSearch. If your code is encountering an error and it is hooking the aftersearch event then the pagination does not get re-enabled. It might actually be prudent to wrap your aftersearch function in a try/catch to prevent this condition should there be an error

[Vinh]

Chris,

We've actually just finished adding a way for coders to bind to various events. It'll probably be available next time we push out an update. Here's a sneak peek at the events that will be available:

afterSearch
moreActivity
moreNotification
pageChange
columnSort

When it's live, there'll be more details on how to use it.

[Pebble]

Just wondering if this has been pushed out yet or there is a planned date(ish)

[Chris]

May 14, 2013 23:33:03 GMT -8 Chris said:

It appears there was a Proboards push finally giving the long awaited proboards.events addition so please be patient while authors affected by this change have time to update to this new highly anticipated feature.

proboards.on("pageChange", function(){console.log(arguments.callee.caller.toString())})

$.extend(proboards, {
events: {
afterSearch: [],
afterSearchOne: [],
columnSort: [],
columnSortOne: [],
moreActivity: [],
moreActivityOne: [],
moreNotification: [],
moreNotificationOne: [],
pageChange: [],
pageChangeOne: [],
run: function(f, b) {
...