I've been a bit busy last week, so have some pages to catch up with.

I'm on page 17:

[www.plus613.com]

last image number is 9113, so first image on page 18 should be 9112.
Click "next" and find myself looking at images in the 6000-range.

(Now that I try to find the exact 6xxx number it's suddenly sorted itself out. Anyway, this is the second time this happened today. The first time, a few hours ago, I suddenly found myself looking at those Latvian motorbikes from a couple of weeks ago...)

See this thread: [www.plus613.com]

When an image is removed, its image ID is never used again, so it takes you to a random image as the site won't display whatever was there. We thought that would be nicer than a big "IMAGE DOES NOT EXIST" style page, however when you're voting your way through images I guess we could make it skip to the next 'real' image rather than trying to hit one that's no longer there.

No, I was clicking next between the thumbnail pages. This is a new Bad Behaviour that I saw for the first time yesterday.

Alot of the pages are cached, so maybe what you where seeing was a cache stuffup, but because you can't reproduce debugging is alittle hard.

Sure - if your cache is several weeks old... (yesterday (or should that be the day before?) is also the first time I saw your new way of numbering in the URLs on those thumbnail pages...)

The "new way of numbering" has been in place for weeks, since image category selection in the gallery was enabled.

By the looks of the URL you have there, you have selected to view a specific category.. It's possible either there was a large break in image numbers between pictures voted into that category or .. maybe it doesn't display in order. Not sure.

No, I have not chosen any categories. I have chosen the "gallery" link on the front page:

[www.plus613.com]

then followed "next" until that happened.

Tried it again. Got to page 17, then found myself looking at oooold pictures. No weird URLs this time though. Clicked "back" then "next" again and the problem was gone.

Dunno, I haven't seen anything like it. Chances are it's a caching issue, anonymous users are very heavily cached. If you used a login account, the cache time is dropped massively (and you get your own cache files instead of sharing them with all the other anonymous users) which should remove little quirks like that (assuming that's what it is).