It has been fixed with a complicated-looking few lines of Javascript by Stem_Cell! ^^

See the quote below for information on what was.

Looks like a lot's still in development.

Might be able to help out, if I can get my hands on the code.

Yep. This project has been perpetually in development for at least a couple years now, I believe.

If you want a copy of the code to look over, you can download the source here: code.google.com/p/my-imouto-booru/downloads/list

If you are able to find the magical characters I must enter to fix the forums, well, that would be awesome. :P

I'm mostly sure that the line that generates the page numbers is line 51 of \app\views\forum\show.php, but it looks like the line is solid to me.


It looks as though it's complete, but it's acting as though it's outright ignoring

I believe I've tracked it down for you.

The problem is in line 152 of \vendor\Rails\ActionView\Helper\WillPaginate\AbstractRenderer.php

That's what's creating the page number and next/previous links, and the problem is that there ought to be a specific renderer for Forum posts which includes the action in this link line: instead there is only one AbstractRenderer that creates these links for everything.

The fix is a little complicated, and I'll need to look at the software more carefully to implement it, but it could be that just editing the page number function on line 46 of the same file could give you a quick-fix: the "if" block in that function could be changed to check the type of the collection, and if it is forum post, to include the action=>show in the link.

You could ask the dev, or I could try code it in for you, but it'd be faster just to forward the above to him. I'd have to set it up in my environment to make the fix and test that it doesn't break everything, and that'll take time - but if you get no reply from the dev, let me know and I'll do it.

Thanks Zigg. I'll copypasta what you just told me into the bug report I sent him.

The developer has been distracted by developing the code in some major way as of late, rather than just bug fixing. His time is limited at the moment. I don't mind waiting, but it might be a while. Do with that information what you will. :)

And thanks again for the help.

Thanks for the help, Ziggs. =)

By the way, I can fix this via javascript, it's pretty easy to do.
Would you want me to?

You can?

...I wonder if that would cause problems when the update comes...

I can make it do the following:

if (weAreOnAPostPage() && thereArePageLinks() && thoseLinksAreBroken()) fixTheLinks();

Therefore no problem when updates come.

I may take on the task soon since there seems to be interest.

That would be all sorts of awesome if you would. It's truly the only really annoying bug we have atm.

Ok I don't know how exactly the code structure in a booru source code is but...doesn't it need some code to allocate the pages to the 'page'-buttons? Why did it work earlier?

It didn't. At least not for us, when we started using it. It probably worked in earlier versions, but then something caused the developer to change how something was coded (maybe a new version of HTML or something like that). Either that or he broke it when adding/editing something else entirely, by coincidence.

I've been busy cooking up new back-end stuff for hypnohub-hover-zoom (blacklist support!), now I've just finished doing that and next thing I'll do is make a script to fix those links.

Using a banana testing protocol too?
24.media.tumblr.com/tumblr_m7m6nsrOKL1qjhttjo1_500.jpg

Ah, so there are people other than Vanndril, Mindwipe and Kinkyloli who've noticed the Hover Zoom Thread! :)