I am having trouble authenticating with Railpage using facebook.  Appears to auth but then says I am not.  Just happening tonight. Any recent changes today?

Try again now.

Intriguing. The last visited timestamp isn't all that important anymore  

It must be of supreme importance when viewing posts since last visit!

I notice that if I mark all forums read, then exit and return, they are all back to being un-read again. Even marking 'all threads read' does not work within a given forum.

Intriguing. The last visited timestamp isn't all that important anymore  

It must be of supreme importance when viewing posts since last visit!

It's really not. I could even post the sections of code that determine new post statuses.

I notice that if I mark all forums read, then exit and return, they are all back to being un-read again. Even marking 'all threads read' does not work within a given forum.

Yes, I touched on that earlier. Marking a thread as read is fine, but marking a forum as read is broken.

I notice that if I mark all forums read, then exit and return, they are all back to being un-read again. Even marking 'all threads read' does not work within a given forum.

Yes, I touched on that earlier. Marking a thread as read is fine, but marking a forum as read is broken.

Aha, OK, now I get the distinction.

Aha, OK, now I get the distinction.

It all dates back to the horrible, horrible phpBB 2.x code. I've just made some changes which should hopefully fix the forum read/unread bug

Images like https://www.railpage.com.au/image?provider=flickr&photo_id=20485198376 do not always load on the first click.  A reload of the page is required.

Intriguing. The last visited timestamp isn't all that important anymore  

It must be of supreme importance when viewing posts since last visit!

It's really not. I could even post the sections of code that determine new post statuses.

Can you explain in simple terms? To me it just makes sense that to display new posts since your last visit the software needs to determine when you last visited...

Don't bother posting the code, likely I wouldn't understand it (unless it is BASIC, DIBOL, COBOL, Datatrieve etc)

Ok: a decade ago, when you logged into Railpage your last visited timestamp was updated to the last session timestamp, which was updated on every page generation.

There are two problems with that: if you log into Railpage from another device at the same time, it resets that timestamp, and it added an extra db query to every single page generation. This impacted the performance of our database server.

Along with that, your list of read threads was stored in a cookie on your browser. That was how Railpage knew not to flag read threads as unread. Which is a well and good, if you use Railpage from only one device.

So I changed the session time update to happen at random once every five page generations, which of course affected the last login time. Not only that, but the concept of basing read/unread threads against a point in time is stupid: if I log into Railpage and don't get round to reading the unread threads before my session expired and I had to log in again, those threads became read. So, we now store the list of read threads and forums in memcached, falling  back to cookies as a fail-safe. We also store then in the database in a more efficient manner, which helps for watched threads.

the concept of basing read/unread threads against a point in time is stupid

Understood and agreed, but it doesn't answer my question with regard to the "View Posts Since Last Visit" function. Also Mark All Forums read still doesn't work.

the concept of basing read/unread threads against a point in time is stupid

Understood and agreed, but it doesn't answer my question with regard to the "View Posts Since Last Visit" function.

You agree with my point that showing new posts since a point in time is stupid, but want the "View posts since last visit" function - a point in time function - to work as it used to? Or am I missing something?

I no longer understand what it is that you're unhappy about.

the concept of basing read/unread threads against a point in time is stupid

Understood and agreed, but it doesn't answer my question with regard to the "View Posts Since Last Visit" function.

You agree with my point that showing new posts since a point in time is stupid, but want the "View posts since last visit" function - a point in time function - to work as it used to? Or am I missing something?

I no longer understand what it is that you're unhappy about.

I'm not unhappy at all! There is a button labelled "View Posts Since Last Visit". I can't understand how this can now work...
Edit: When I click the abovementioned button, I get a listing of all posts since my last visited date, which is (still) incorrect. I'm not unhappy about this, I don't even use this function, but it is there and can be used and doesn't do what it says, thus it is a bug.

Also, I have replied to your PM with 3 different responses, but the system tells me that you haven't read my responses. No pressure, but you asked me a question and I have given you answers.

Every time I log on (at least once per day) it shows my last time of logging on as being August 8. I have reset the log on date several times but it still reverts to August 8 on the next visit. As I am only interested in a few threads, it is becoming a pain.

Every time I log on (at least once per day) it shows my last time of logging on as being August 8. I have reset the log on date several times but it still reverts to August 8 on the next visit. As I am only interested in a few threads, it is becoming a pain.

Not two posts up we just had a discussion about the last visit timestamp, and why resetting it on each and every login is stupid and thus no longer happens.

Every time I log on (at least once per day) it shows my last time of logging on as being August 8. I have reset the log on date several times but it still reverts to August 8 on the next visit. As I am only interested in a few threads, it is becoming a pain.

Not two posts up we just had a discussion about the last visit timestamp, and why resetting it on each and every login is stupid and thus no longer happens.

See my post (three up) as to why it is not stupid. If we are not going to do this you need to:

1. Remove the display of "Your last visit was...".
2. Remove the "View Posts Since Last Visit" button.

As they have been rendered irrelevant.

There is a new link in TRNs to unsubscribe from reply notifications.

When it is clicked for this topic (at least) it links to the following message:

Error





Home
The page you requested does not exist.

This can be caused by an out-of-date link or bookmark, or a mis-typed address. It might even be a momentary problem at our end! Please try again.

There is a new link in TRNs to unsubscribe from reply notifications.

When it is clicked for this topic (at least) it links to the following message:

Error

Home
The page you requested does not exist.

This can be caused by an out-of-date link or bookmark, or a mis-typed address. It might even be a momentary problem at our end! Please try again.

Should now be fixed

Attempting to tag 8140 coming into Bunbury Street today.  Selected the right loco and clicked TAG. Received an error which looks to have been caused by a broken URL.

https://www.railpage.com.au/modules.p%20h%EF%BF%BD#X��Railcams&mode=photo&permalink=bunbury-street&id=20018206914&loco_id=1053

Every time I log on (at least once per day) it shows my last time of logging on as being August 8. I have reset the log on date several times but it still reverts to August 8 on the next visit. As I am only interested in a few threads, it is becoming a pain.

Not two posts up we just had a discussion about the last visit timestamp, and why resetting it on each and every login is stupid and thus no longer happens.

See my post (three up) as to why it is not stupid. If we are not going to do this you need to:

1. Remove the display of "Your last visit was...".
2. Remove the "View Posts Since Last Visit" button.

As they have been rendered irrelevant.

I note that the "Your last visit was..." now updates and thus the "View Posts Since Last Visit" works as it should. However, it has gone back to marking all posts read when you log out like it used to. I actually don't mind this, but we did agree above that this behaviour is stupid!

I note that the "Your last visit was..." now updates and thus the "View Posts Since Last Visit" works as it should. However, it has gone back to marking all posts read when you log out like it used to. I actually don't mind this, but we did agree above that this behaviour is stupid!

Actually, no. If you log out now and log back in, those same unread posts should remain unread.

The only time your last visit timestamp will now change is if the time between your last session timestamp (updated at five minute intervals) and now is greater than the default session time, which is an hour. Unless there's another bug which my testing has not uncovered.

I've put this change in because your opinion on the matter seems to have changed back and forth between "it's stupid" and "it's not stupid", and I've had enough of it.

I've put this change in because your opinion on the matter seems to have changed back and forth between "it's stupid" and "it's not stupid", and I've had enough of it.

No, my opinion has not changed at all.

• It is stupid to display a last visit time that is incorrect.
• It is stupid to have a button that says "View Posts Since Last Visit" that actually displays posts since the incorrect last visit date/time.
• It is NOT stupid for unread posts to remain marked unread across sessions, most forums operate this way. However, because Railpage had always been the other way, I had become accustomed to using the Time Machine and/or Mark All Forums Read (which still doesn't work) when I had to!

That has always been my position. I don't believe I have ever stated differently (although my wording has probably been different, and as you increased my understanding by explaining things I have likely modified the way I expressed my opinions).

If you log out now and log back in, those same unread posts should remain unread.

Tested and it did, but the last visit time didn't update.

The only time your last visit timestamp will now change is if the time between your last session timestamp (updated at five minute intervals) and now is greater than the default session time, which is an hour. Unless there's another bug which my testing has not uncovered.

I'm not sure I fully understand that. Does it mean that you have to be logged out for an hour for your last visited date/time to update? If the last visited date/time updates do all forums then get marked read? I don't believe they should (see previous post).

Could you please respond to my earlier query with regard to "No post mode specified".

I still regularly have my posts failing to be submitted, getting the message "No post mode specified".  Despite several attempts in querying this, I'm still waiting for a response.

When this happens, what amount of time passes between loading the page containing the reply box (either quick reply or a full reply) and pressing submit?

It  appears that TRN's to my subscribed threads have ceased since approximately 6pm yesterday, even though the threads have had replies.