31

So, just out of curiosity … What's up with that, SO devs? Well, back in the day we used to use direct queries to SQL Server to build up the various question sort pages. This worked fine for a while, and Smurfs were happy. However, slowly, over time we discovered that for our specific use SQL is just not fast enough. I posted a question on theoretical CS ...


11

If a user wanted to only page through 13 questions at a time, they can do that if they wanted to hack the URL. If you wanted to page through one question at a time, for whatever reason, you could change the URL to &pagesize=1. 15, 30 and 50 are the default page size options presented. 50 questions is the maximum. You can try and enter a higher number, ...


9

Switching between pages in the inbox now appends a ?tab=inbox&page=# to the URL for easier pagination. The pagination links also now correctly point to the same page, so right clicking and opening in a new tab/window won't take you to an unstyled page anymore.


8

This isn't a bug - the system is doing exactly what you ask, which is giving you questions 16-30 in the current list. "The current list" is a different list pretty much every time you ask for it, of course, but that doesn't change what you asked for. What you may be interested in is the answer to this question: RSS feed of your favorite tags. If you want to ...


8

A fix for this went out with the latest build.


6

Workaround to load specific page is pasting the following into JavaScript console of the browser: var desiredPage = 12; var desiredLink = $("#inbox-pager").find("a").first().attr("href").split("=")[0] + "=" + desiredPage; $("#inbox-container").load(desiredLink, function () { $.scrollTo($("#inbox-container")); }); Just change the desired page, press Enter ...


6

This wouldn't actually work in any generic way, since they aren't ordered by Id, the orders are all over the place...some are based on last edit, last activity, when the bounty ends, how many views they have, how many votes...all of which are in flux an don't lend themselves to a linear list. This hasn't really been a problem historically, especially since ...


6

A fix for this is rolling out as I type.


5

This is the question: How to get the value of the textbox which created dynamically with the Raduploader in code behind? It has five tags: c#, javascript, jquery, asp.net and telerik. You have one of those tags in your "ignored tags" list plus you have "hide ignored tags" in your prefs: This caused the question to be hidden after the page is loaded.


5

Thanks for the diagnosis re SSL, that's exactly right. Our pagination links were hard-coded to http, which is obvs wrong. Try it again?


4

You can change the URL: http://stackoverflow.com/questions?page=(THE_PAGE_NUMBER)&sort=newest But why do you want to do this?


4

I personally don't think this is worth doing. Semantically speaking, having the "current" page be clickable makes little sense to me. And there are typically better ways to refresh pages either via keyboard shortcuts or by hitting the "refresh" button in the browser that's generally available on touch devices as well.


4

It pains me to remove an "off by one" error, but if I must, I must.


4

As far as I can tell this has been implemented, along with other /review display options such as date range filters and sort order. I've tested this by selecting the page size (and filter/sort options). This resulted in the following querystring: ?s=1&pagesize=50&filter=month&customsort=shortest&no-random=1 Then, upon loading /review on ...


4

Here's a screenshot of a particularly inopportune moment on the 'newest' page. Sorry for the length, but this is the resized version. The larger version is how it looks for me all the time. You just have to scroll through it once. I'll admit that this is a particularly bad case, there are usually 5-10 questions, but fewer isn't that uncommon) There ...


4

I've fixed this in a userscript. // ==UserScript== // @name SE Chat Ignore List Fix // @description Fixes broken chat ignore list. // @version 1.0.0 // @date 2016-02-22 // @author Eyeballcode // @contact eyeballcode@gmail.com // @namespace http://eyeballcode.github.io/se-chat-ignore-fix/ // @include *://chat....


3

Just bringing this back to the surface to highlight the issue with the current League of Legends contest over at gaming.se. Hiding just league-of-legends (zoomed for emphasis, also there is a bug in the sidebar when zooming): 9 out of 50 questions being displayed.


3

Per screen shot it looks like you use default setting to display 15 questions per page. Per my recollection, "reappearing questions" were indeed a noticeable annoyance with this setting. To me, the annoyance has gone when I changed settings to display 50 questions per page: Not that above change magically fixed Next page - quite opposite, there are ...


3

As you see, you went to the page where there are only deleted answers or no answers. Each normal page with answers has a pager at the top and in the bottom, and between these pagers answers are located. But you can't expect it to work properly when you go to the empty page (which can be done only via link, the pager itself never has links empty pages).


3

I agree, it can be quite annoying. However, so can being taken to completely the wrong page. My suggestion would be to do some calculations, so that it'll actually end up back in the same spot. So, if you're on page 3 for 15 items per page, and you switch to 30, it should take you to page 2. ceil((15 * 3) / 30) == 2


2

I get an uncaught Security Error in Chrome (looking in the Developer Tools) Uncaught SecurityError: A history state object with URL 'http://careers.stackoverflow.com/jobs?searchTerm=&pg=2' cannot be created in a document with origin 'https://careers.stackoverflow.com'. jobs.min.js?v=8525c7a8307d:1 (anonymous function) jobs.min.js?v=8525c7a8307d:1 c ...


2

Pagination oopsie un-oopsied now. The pager code has been recently changed (in part to support localization and in part to make it better) and this issue has escaped notice (as it appears to happen only in certain locations and not the main tested ones).


2

The best reason I could see you might want to browse to the middle is if you are scanning for questions with a specific vote count, or in a specific range of votes, and much of that you can accomplish with a search, for example: Search for XML-tagged questions with a score in the range of 22 to 45 This search leaves you with just 180 (as of this writing) ...


2

I think that would add unneeded clutter. It's rare that I want to go to a specific page that isn't the first, last, previous, or next page. If I want to go to a page in the middle I can edit the URL.


2

Well, that's just annoying! Some glitch; it wouldn't be very interesting to go into details, other that to say "it didn't quite do what we wanted it to". It is being a bit more obedient now, I think.


2

I'm offering a bit of a non answer here, which explains why this happens and possible approaches to fix. Review eliminates already reviewed items from the list ... if you already reviewed 15 items and head to page 2 (with 15 per page) we eliminate the 15 you already reviewed from the list and head to page 3. To get pagination to work properly we would ...


2

This was fixed as of 3de4a2c, thanks for the report!


2

Same issue as here, but in a different part of the code. The fix is out in production now.


1

Is there a way to make the pagination bar appear on top of the answers list? As you tagged this question as feature-request I don't feel this feature is required because just by pressing End or Ctrl+End you can go to the end of the page and select the next page. Is there a way to apply sorting on the results so that I can sort the results by date Why ...


1

The problem was here: Regex _removePage = new Regex(@"page=\d+&", RegexOptions.Compiled); We used to ensure the page was stripped off the page sizer's URL, effectively kicking you back to page 1 in all cases. When we switch to razor and no longer had to encode the URLs in our strings, & became & and the stripping of page number just ...


Only top voted, non community-wiki answers of a minimum length are eligible