QUOTE (Zyerne @ Nov 5 2010, 08:27 PM)
I'm also have log in weirdness. Says I'm logged in, but as I click through the forums. some pages will tell me I'm logged in, some won't. Sometimes I can make replies, sometimes I can't same with starting new threads, getting a log in message. Logging in at that point gets me the logging in now message followed by the same not logged in error.
Help?
Edit: Seems like to be able to make new thread, I have to convince it to let me to reply to an existing thread, then my log in sticks.
looks like either a cookie or a cache settings issue to me (or possibly both)
further explained : most sites track wether you are logged in via using cookies, so in case you are using temporary cookie settings instead of persistent ones for this site, a new cookie might be generated missing your userid/passwordhash/sessionid or whatever thus recreating the 'not-logged-in' state.
if this is your problem try to alter your cookie settings for dumpshock to ALLOW for this domain or something similar...
another possible issue might be browser caching settings. in case you are using cache to retrieve site content you have accessed before, it might display the old server-generated php site with the same URL (stored in memory cache) instead of retrieving all the content fresh from the server. examples would be firefox-plugins like BetterCache or some custom about:config or similar browser settings.
for example if i click quote in a dumpshock thread and im not logged in yet it (correctly) redirects me to the login page instead. after logging in (setting the cookie information) it takes me back to the original URL (the quote target URL), but since my browser cached that page to redirect me it will again redirect me to the (cached and thus pre-logged in version of the) login page. (so the server knows im logged in and WOULD generate the CORRECT content if my browser would request the site content, but my browser is using the old rrequested pre-login data instead due to my custom browser cache settings).
Another reload this time bypassing the page and actually refreshing the content from the server usually resolves that issue.
in case its anything else it is probably a server issue, but if one of the above solutions worked for you the problem is on your side (the browser/client side)
hope that helped
gl hf =)