No.1853
>Not using the damn index bar buttons
Try those.
No.1855
Over in the top category of the index bar to the left (the 'Uboachan' category that starts with [News]), there's options for [YB], [Y], [U], [UG], and [RZ]. Those change the color scheme.
No.1856
The page bottom links still work for me on vanilla Firefox. There's probably a compatibility issue with Flux. Making Javascript work across frames is a fucking nightmare.
No.1857
>>1856Yeah, the links at the bottom of the page don't work for me.
P.S.
I'm using Chrome 35 on Windows 7.
No.1858
>>1857Well fuck. If it works on Chrome, it doesn't work on Firefox. If it works on Firefox, it doesn't work on Chrome. I've hacked at this problem a dozen times and it keeps resurfacing. The reason is that different browsers have different non-standard functionality for protecting stupid users from Javascript cross-site-scripting, which means each browser has arbitrary and different steps required to run a Javascript function across frames. This gets very confusing and retarded. A previous software update probably broke it again. This is gonna suck.
No.1859
>>1858Wouldn't it be more convenient to just take those buttons off the page and use the index bar buttons instead?
Because, if every software update it's breaking it for no good reason, and it's a pain in the ass to fix, the best solution seems to be to stop using them.
No.1860
<a href="javascript:void(0);">[Rei/Zero]</a>
Yeah, all I get is a void on chrome.
No.1861
>>1859I could do that or try to fix it one more time. Tinyboard is winding down as a project anyway, all that's being pushed is mostly bugfixes and small features.
Eventually I'd like to replace this software with some new software, and merge in posts from the current site AND the archive. That would be cool.
No.1862
I second this motion.
No.1863
>>1858Not sure if you already know this, but what I've noticed is that the buttons on the bottom work fine when Frames are on, but do nothing when frames are off. I usually browse with the latest version of Firefox, but after testing quick, it seems this behavior is consistent in the latest version of Internet Explorer and Chrome as well.
No.1864
>>1863Oho, a lead! This should be an easy fix
when I get around to it.