What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

While editing the long FAQ, I noticed that many automatic titles of raw links are not shown in the preview.

On page load I see a single XHR that, for example, includes question id 11740. But 11740 is not in the results, unless I replay that request and limit the number of ids. It seems the results are paginated, but no additional Ajax calls are made to get the 2nd and 3rd set:

apiCallbacks["meta.stackoverflow.com"]({
  "total": 63,
  "page": 1,
  "pagesize": 30,
  "questions":
     [...]

(After page load, when chancing the troublesome URLs, I'm not seeing new Ajax calls for the troublesome URLs — but I guess that's just caused by some caching you're doing? Nice! Same results in Safari, Firefox and Chrome on a Mac.)

share|improve this question
    
Yep, I didn't take pagination into consideration. The FAQ is probably the only post where that matters :) –  balpha Mar 15 '11 at 13:33
    
@balpha, I actually posted here (rather than commented on Can we improve the automatic titling of links to internal URLs?) so you can easily tag status-bydesign! –  Arjan Mar 15 '11 at 13:36
    
@Arjan: It's a trivial fix; might as well make it status-completed –  balpha Mar 15 '11 at 13:37
    
You're not just increasing the page size, @balpha? ;-) –  Arjan Mar 15 '11 at 13:39
    
@Arjan: I know you'd just create a post that surpasses that page size :) No, the implementation for this is a queue anyway, so making sure this queue only handles 30 questions at once was all that's necessary –  balpha Mar 15 '11 at 13:54
    
I sure would have! So now I'll have to make a post with 29 or 31 links, to validate, @balpha ;-) (Actually, one wouldn't even have to save such post: I like the way the Ajax calls are combined into one call, even when just pasting the Markdown of the FAQ into a new unsaved, post. Nice, very nice!) –  Arjan Mar 15 '11 at 14:00

1 Answer 1

up vote 1 down vote accepted

This is really a pathology (the FAQ is probably the only page where this even matters), but the fix was easy enough, so this will work after the next build.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .