Problems with newest posts

Started by dochira · 5 Nov 2004 · 6 replies

Suggestions & Announcements Page 1 of 1

5 Nov 2004, 15:33 #1
When I click on the "newest post" icon for the topic, it always goes the first newest post after I logged in, not the absolute newest posts to the thread. (Did that make sense?) Is this a bad cookie thing because I always end up logging off then logging back in to fix it temporarily.
5 Nov 2004, 15:37 #2
That occasionally happens to me, after I go from old to new, new to old and so on...
14 Dec 2004, 14:45 #3
This is a followup to this problem. Now when I click on the unread post icon (the orange plus sign), it also clears the unread posts of the thread above it. I am using Firefox, BTW.
14 Dec 2004, 14:57 #4
i think it's just cookie prob. i'm encountering the same prob. anyways :mrgreen:
14 Dec 2004, 15:16 #5
dochira wrote:This is a followup to this problem. Now when I click on the unread post icon (the orange plus sign), it also clears the unread posts of the thread above it. I am using Firefox, BTW.

I'll take a SWAG* at this...

I think the problem is because the server hosting JDorama.com is timing out, closing your current session with JDorama.com. Then, when you connect back to JDorama.com, it's basically a new session. More likely you may not even notice the drop!

JDorama.com is based on phpBB 2.0, which tracks its user sessions by a session ID number (SID). phpBB runs on top of Apache server, which also has its very own internal session ID number. Anytime a session is timed out within Apache, it more likely affects phpBB, and therefore the user's session with JDorama.com. Effects of a session timeout include resetting of all of settings within your JDorama.com profile, for example your last login date/time, which is how the system determines the posts that have been made since your last visit.

To show how quickly a session can timeout within Apache, log onto JDorama.com with your web browser. Right after you log on, close all of your web browser windows. And then immediately re-logon with JDorama.com. Even though you were just logged on less than minute before, you're running under a different session within JDorama.com.

zchendevlemh is actually correct about the cookie thing. However, it's the SID that's stored in the cookie. So when the session is reset, the SIDs don't match.

So why the session timeouts? It's possible that the drops occur when the hosting server is being flooded with processes.

--- groink

*SWAG = super wild ass guess
14 Dec 2004, 15:20 #6
groink wrote:
I'll take a SWAG* at this...

I think the problem is because the server hosting JDorama.com is timing out, closing your current session with JDorama.com. Then, when you connect back to JDorama.com, it's basically a new session. More likely you may not even notice the drop!

JDorama.com is based on phpBB 2.0, which tracks its user sessions by a session ID number (SID). phpBB runs on top of Apache server, which also has its very own internal session ID number. Anytime a session is timed out within Apache, it more likely affects phpBB, and therefore the user's session with JDorama.com. Effects of a session timeout include resetting of all of settings within your JDorama.com profile, for example your last login date/time, which is how the system determines the posts that have been made since your last visit.

To show how quickly a session can timeout within Apache, log onto JDorama.com with your web browser. Right after you log on, close all of your web browser windows. And then immediately re-logon with JDorama.com. Even though you were just logged on less than minute before, you're running under a different session within JDorama.com.

zchendevlemh is actually correct about the cookie thing. However, it's the SID that's stored in the cookie. So when the session is reset, the SIDs don't match.

So why the session timeouts? It's possible that the drops occur when the hosting server is being flooded with processes.

--- groink

*SWAG = super wild ass guess


we've been aving session problems with our application too so i'm kinda relate to groink's SWAG (damn!! it's cool new word for me)
14 Dec 2004, 16:17 #7
groink wrote:
I'll take a SWAG* at this...
...
*SWAG = super wild ass guess


Thanks groink. I'm sure the problem will go away in due time. At first I thought you said you'd take a SWIG at this.... :drink: :sweat: :hehe:

Replying needs an account. Registration opens soon.