Home » Forum » Bug Report and Feature Requests

Forum: Bug Report and Feature Requests

Missmatch between stories accessed and story count



I keep a list of stories I'm interested in; previously this was just browser bookmarks in a folder, but now it is a text list of just the story IDs. I have a number of script tools to support this, most useful being some which give me the capability to drag-and-drop a browser link onto a target, which then (if it's a SOL link) isolates any story IDs and adds them to this list, optionally at the beginning of the list (for 'about to be archived', which need prompt treatment), and preventing any duplicates. I can load a story from the list by accessing https://storiesonline.net/s/{story id} as this was previously the format for story links, although they are now

https://storiesonline.net/s/{story id}/{story title}; I still have bookmarks in the first form and other people seem to have them, too.


Accessing a story through the first form of link quite correctly updates the stories accessed count, and lists the story on the 'today's accesses' page (eventually, as the first form of link doesn't seem to invalidate the cache - that's probably A bug, but not THIS bug). However, subsequently accessing the story through the link on the 'today's accesses' page (which is of the second form) accesses the same story but increments the stories accessed count again! The home page would/does then read 2 accesses, but the 'today's accesses' page only lists one story.

After I'd reported what appears to be an instance of this with home page story counts of [17/16], Lazeez seems to have put in a 'fix' that checks the headline count before allowing access. This results in access being disallowed at a homepage count of 16, where the actual count accessed and reported on the 'today's accesses' page could be considerably lower.

I think I saw a manifestation of a different form of this shortly before the recent database maintenance; at that time, the homepage 'up for archive' link was served as www.storiesonline.net/... and stories listed therein were also www.stories...; accessing these then accessing again through the 'today's accesses' page seems to have double-counted the accesses.

Lazeez Jiddan (Webmaster)


URL form or where you access the story from has no effect on this. There is only one story delivery mechanism and it's triggered for any story access.

The problem could be a cache/database sync problem, and it could be something else.

If/When you notice this again, let me know as fast as possible and try (if you can) to refrain from accessing stories anymore until I get to see what's going on.

Replies:   madnige

@Lazeez Jiddan (Webmaster)

OK, I've forced it to happen: [2/16] on home page, one story listed on todaysAccesses. I'll aim to not access another story before 2017-10-20T13:00Z (about 19hr), then there'll be a flurry of accesses, if you then want another sample, request here by 2017-10-20T14:00Z. The first access is nice and quick, but then there's quite a wait until I get a populated todaysAccesses; is there a non-download way I can invalidate the cache?

Lazeez Jiddan (Webmaster)


OK, I've forced it to happen: [2/16] on home page, one story listed on todaysAccesses.

That's so odd that you could reproduce it reliably. I've been unable to, no matter how many permutations of the URL I've used.

I need the exact a step by step sequence you used to replicate it. Tools used, URLs accessed etc...

I've made one change to make sure the story delivery mechanism has no sync issues with the cache. I don't know if it will fix it. If it doesn't, then I need those exact steps to see if I can figure out what's going on.


System details are as previously reported except now Firefox 56.0 (32 bit, Ubuntu, canonical 1.0),;

Initial access by wget (options) https://storiesonline.net/s/$storyid (plus cUrl to get moreData.php for the story) - this time it's story id 71015 and the story access count has increased from 2 to 3; the todaysAccesses as updated immediately (previously it was delayed >10 min). Clicking on the link for 'Snow to Bed' (the referenced story) on todaysAccesses accesses the story as expected but does NOT now incorrectly increase the story access count so it seems the change has effected a fix as well as correcting the slow update issue. Thank you very much for your superb service.

ETA: Could it have been the different clients, in which case would it have occurred with people accessing from both mobile phone and desktop computer with different browsers?

Back to Top