"Previous" and "Next" buttons not working

[newmajorpanic]

Hopefully not because I'm an idiot, but the "previous" and "next" buttons in multi-page threads seem not to be working for me at all!

[Brother Tyler]

What theme/device are you using? I just tested both buttons on my computer using Microsoft Edge and Mozilla Firefox and both worked on both browsers. I also tested both buttons on my phone (Samsung Galaxy) using the Mozilla Firefox app and they worked there, too. I noticed a bit of delay between activating the button and the screen changing, but that was only a second or so.

[sibomots]

Please provide a link to the page when this behavior was noticed.

I need something to start from when diagnosing the problem.  Thanks.

 

[newmajorpanic]

Weird. It's still happening. For example, if I head to the State of the Union (Heresy) thread - https://bolterandchainsword.com/topic/369602-state-of-the-union-heresy/page/191/#comments it is still happening.

I'm on the latest version of Firefox on a PC - it doesn't happen on mobile. Hope that helps.

[sibomots]

7 minutes ago, newmajorpanic said:

Weird. It's still happening. For example, if I head to the State of the Union (Heresy) thread - https://bolterandchainsword.com/topic/369602-state-of-the-union-heresy/page/191/#comments it is still happening.

I'm on the latest version of Firefox on a PC - it doesn't happen on mobile. Hope that helps.

I followed that Link.

It took me to page 191  of that thread.

I pressed Next

I went to page 192 of that thread.

I pressed Prev

I went to page 191 of that thread.

I pressed Prev

I went to page 190 of that thread.

I'm using Chrome on Winblows 10.

On Edge it's another matter.

On Edge, when not signed in, when browsing anonymously:

The button does not appear.

But on Edge, after signing in, the button does appear:

 

So the $64,000 question is -- were you signed in or signed out?

 

 

 

[newmajorpanic]

6 hours ago, sibomots said:

So the $64,000 question is -- were you signed in or signed out?

 

Fascinating. I was signed in!

[appiah4]

Also having this issue.  In addition to Next/Prev direct page numbers do not work for me either.

[selnik]

I am having the same issues, on the latest version of Firefox for PC. Signed in.

[sibomots]

7 hours ago, appiah5 said:

Also having this issue.  In addition to Next/Prev direct page numbers do not work for me either.

 

55 minutes ago, selnik said:

I am having the same issues, on the latest version of Firefox for PC. Signed in.

Same URL?

Chrome, Firefox, IE, Edge, Netscape, AIR Mosaic, XMosaic, Opera ?

The URL I was testing above had 192+ pages to it.

Have you tried other sample-sizes.. Threads with 1-2 pages  5-10,  10-30 etc?

We know from your observations that there is a problem.   The next thing I'd like to do is correlate it with some other data:

• Number of pages
• Browser

Thx. This is helpful.

 

[dorath]

Also experiencing these problems.  No Previous or Next, and none of the links in that block are working.

Edge Version 103.0.1264.37 (Official build) (64-bit)

Number of pages in the thread does not seem to matter, nor does being signed out or in.

Tried with the following
2 pages: https://bolterandchainsword.com/topic/374650-attached-images-in-signatures/

6 pages: https://bolterandchainsword.com/topic/374546-welcome-back/

13 pages: https://bolterandchainsword.com/topic/340641-shapeways-the-reliquary-store-twin-rifles-more-pads-and-posable-maedic-gauntlets/

28 pages: https://bolterandchainsword.com/topic/372773-the-12-months-of-hobby-2022/

61 pages: https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/

Here is the ipsPagination block from the bottom links set of the 61 page thread

<ul class="ipsPagination" id="elPagination_881cbcf7450380578a1602c9d7357e71_1340835069" data-ipspagination-seopagination="true" data-pages="61" data-ipspagination="" data-ipspagination-pages="61" data-ipspagination-perpage="25">
		
			
				<li class="ipsPagination_first ipsPagination_inactive"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/#comments" rel="first" data-page="1" data-ipstooltip="" title="First page"><i class="fa fa-angle-double-left"></i></a></li>
				<li class="ipsPagination_prev ipsPagination_inactive"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/#comments" rel="prev" data-page="0" data-ipstooltip="" title="Previous page">Prev</a></li>
			
			<li class="ipsPagination_page ipsPagination_active"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/#comments" data-page="1">1</a></li>
			
				
					<li class="ipsPagination_page"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/2/#comments" data-page="2">2</a></li>
				
					<li class="ipsPagination_page"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/3/#comments" data-page="3">3</a></li>
				
					<li class="ipsPagination_page"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/4/#comments" data-page="4">4</a></li>
				
					<li class="ipsPagination_page"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/5/#comments" data-page="5">5</a></li>
				
					<li class="ipsPagination_page"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/6/#comments" data-page="6">6</a></li>
				
				<li class="ipsPagination_next"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/2/#comments" rel="next" data-page="2" data-ipstooltip="" _title="Next page">Next</a></li>
				<li class="ipsPagination_last"><a href="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/page/61/#comments" rel="last" data-page="61" data-ipstooltip="" _title="Last page"><i class="fa fa-angle-double-right"></i></a></li>
			
			
				<li class="ipsPagination_pageJump">
					<a href="#" data-ipsmenu="" data-ipsmenu-closeonclick="false" data-ipsmenu-appendto="#elPagination_881cbcf7450380578a1602c9d7357e71_1340835069" id="elPagination_881cbcf7450380578a1602c9d7357e71_1340835069_jump">Page 1 of 61 &nbsp;<i class="fa fa-caret-down"></i></a>
					<div class="ipsMenu ipsMenu_narrow ipsPadding ipsHide" id="elPagination_881cbcf7450380578a1602c9d7357e71_1340835069_jump_menu">
						<form accept-charset="utf-8" method="post" action="https://bolterandchainsword.com/topic/335253-duskraiders-40k-nurgle-an-experiment-in-flesh-and-machine/#comments" data-role="pageJump" data-baseurl="#">
							<ul class="ipsForm ipsForm_horizontal">
								<li class="ipsFieldRow">
									<input type="number" min="1" max="61" placeholder="Page number" class="ipsField_fullWidth" name="page">
								</li>
								<li class="ipsFieldRow ipsFieldRow_fullWidth">
									<input type="submit" class="ipsButton_fullWidth ipsButton ipsButton_verySmall ipsButton_primary" value="Go">
								</li>
							</ul>
						</form>
					</div>
				</li>
			
		
	</ul>

 

Edited June 28, 2022 by dorath

[selnik]

20 hours ago, sibomots said:

Same URL?

Chrome, Firefox, IE, Edge, Netscape, AIR Mosaic, XMosaic, Opera ?

The URL I was testing above had 192+ pages to it.

Have you tried other sample-sizes.. Threads with 1-2 pages  5-10,  10-30 etc?

We know from your observations that there is a problem.   The next thing I'd like to do is correlate it with some other data:

• Number of pages
• Browser

Thx. This is helpful.

Tried same URL as in post 4, had same issue. Experience the same issue in other threads with 4, 13, 30 pages, same result. Also experience the issue with the main forum pagination nubmers as in image below.

Firefox 102.0 on Windows 10.

[sibomots]

The worst thing about a bug like this is the answer that will be given as:

"it works for me."   You don't want to hear it, I understand.

I don't like that answer because it doesn't help you.   

I can do some digging on the IPS Forums looking for known bug reports with FF not working in IPS 4.X.

 

Edited July 4, 2022 by sibomots
typo caught by moderator. I had no idea. thx.

[selnik]

3 hours ago, sibomots said:

The worst thing about a bug like this is the answer that will be given as:

"it works for me."   You don't want to hear it, I understand.

I don't kike that answer because it doesn't help you.   

I can do some digging on the IPS Forums looking for known bug reports with FF not working in IPS 4.X.

 

No worries, thanks for looking into it

[Dr. Clock]

Similar issue consistently occuring for me pretty much as noted by dorath: all thread page navigation buttons in the top and bottom bars do not left-click through.

I can get to any of the pages from /forum directory pages as normal, but once in a thread, the nav buttons won't accept a left-click.  The URL is there, and I can right-click 'open in new tab' to get to the right page, but left-click doesn't work on them. The 'Page Number > Go' function embedded in that bar also does not work; although I can type a number into the field, left-clicking 'Go' does not do anything.

macOS 11.6

Firefox 102.0

Cheers,

The Good Doctor.

[tkni]

I'm also running into this, both firefox and chrome on a mac.

The issue, per chrome's console error, is that it is trying to push a non-secured url into the history state on a secured domain.

You can test this by deliberately visiting the site on a non-secure link - http://bolterandchainsword.com - if your browser lets you, and the next/prev buttons will then work.

The full console error:

Uncaught DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'http://bolterandchainsword.com/topic/249255-tabula-astartes/page/3/' cannot be created in a document with origin 'https://bolterandchainsword.com' and URL 'https://bolterandchainsword.com/topic/249255-tabula-astartes/page/2/#comments'.
    at h.pushState (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:56:20942)
    at baseController._updateURL (https://bolterandchainsword.com/uploads/javascript_global/root_front.js?v=a073822eab1656525454:66:9)
    at baseController.paginationClick (https://bolterandchainsword.com/uploads/javascript_global/root_front.js?v=a073822eab1656525454:64:45)
    at nr (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:1:7597)
    at HTMLDivElement.<anonymous> (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:1:8025)
    at HTMLDivElement.<anonymous> (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:1:1076)
    at HTMLDivElement.dispatch (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:2:43090)
    at v.handle (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:2:41074)
    at Object.trigger (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:2:71513)
    at HTMLUListElement.<anonymous> (https://bolterandchainsword.com/uploads/javascript_global/root_library.js?v=a073822eab1656525454:2:72108)

 

[selnik]

9 hours ago, tkni said:

You can test this by deliberately visiting the site on a non-secure link - http://bolterandchainsword.com - if your browser lets you, and the next/prev buttons will then work.

Confirmed, I turned of https-only mode in Firefox and the next/prev buttons worked properly.

[sibomots]

I use Chrome and didn't have to make any adjustments.  The Prev/Next always worked.

I have not trialed the site through FF yet.

 

[sibomots]

17 minutes ago, sibomots said:

I use Chrome and didn't have to make any adjustments.  The Prev/Next always worked.

I have not trialed the site through FF yet.

 

I just downloaded and installed FF.  Made no adjustments to the configuration of FF.  Straight from Install to B&C to the Link.

I visited the link:

The Prev/Next buttons worked.

I cannot replicate this bug.

Platform:

Windows 10, FF

 

[dorath]

8 hours ago, selnik said:

Confirmed, I turned of https-only mode in Firefox and the next/prev buttons worked properly.

Turned off HTTPS Everywhere, dropped the 's' in https from the URL, all navigation buttons work.  Went back to https, found the same Uncaught DOMException mentioned by tkni.

[Dr. Clock]

: )

Thanks, all

So the problem is apparently not with the site as-is... Changing HTTPS-only settings in Firefox wasn't sufficient, I still had to change URL ; )

It appears that my issue occurs only if I use https or www. URLs from my cache. Manually removing https:// puts me comfortably onto "bolteranchainsword.com" URLs and the nav buttons work properly there. I tried to use 'http' ytday as selnik suggested, but looks like using no protocol on the URL at all is the answer for me, just straight to our domain... 

Firefox 102.0 MacOS 11.6

Cheers,

The Good Doctor

[appiah4]

For me the issue seems to happen most (maybe even reproducably so) when I make a post on a thread with multiple pages.  My post registers and the page navigation dies.

[Gederas]

Can also confirm:

HTTPS on Firefox version 102.0.1 (64 bit) doesn't have the previous next buttons working, disabling HTTPS to HTTP worked (tested on multiple threads)

[sibomots]

During the down-time scheduled in week of July 18, 2022, I will be making the changes to turn on HTTPS and deactivate HTTP as default.  The downtime will last 2-3 days.

That will definitely sooth the worries of some Frater over the "OMG not HTTPS?!" and also perhaps resolve this symptom of Prev/Next not functional in some browsers.  I've yet to see a reproduction of the bug in Chrome (Desktop) or FF (Desktop).

But I take for granted that some users are finding it occur.  We will make amends and fix this.   The down-time is when I'll do that.

 

[selnik]

Much appreciated, thanks for all your work on the site.

[tkni]

To confirm, https now being fully enabled for the site has resolved this issue for me.