Login in for each pic

[femalerug]

I´m having some problems viewing the pics. For every one I have been asked to logging in. After seeing the pic, I have to logging in again to see the next one. Am I doing something wrong or is it a program bug?

[femalerug]

Hummm, it´s saying I´m not registered. But I am, I just post a new thread. BTW, I´m using IE 6 and WinXP. Can it be a problem?

[yull]

man, I experienced too your problem.

Solution:

Disconect than re-conect.
Enter in forum main page and here LOG-IN !!
-the login box is in the right bottom of the page
then do all what you want

By

[prik2]

Sometimes I have to logg in for every picture but sometimes not. I hav logged out and in many times but it dosent work. The administrator of this page most help us with this, please!!!!!

I had the same problem in daddo's old site when the paying get startet.....

I hope there will be multipple postings soon...

[John]

This is caused by the server not being able to read the cookie set on your computer. It's not on this end, it is only on the end of the user...either a firewall, browser security setting, etc....wish I could help, but there's nothing I can do....I've looked at every setting. This appears to be most common with AOL users because of whatever default AOL sets in the software... :(

[Unregistered]

do u have a program running that detects cookies and deletes them?
i have 1 and i made sure to accept the 1 that u get on this forum.. then i stayed logged on....

[catwalk]

This problem happend to me once so far. I was logged in, and then for some reason, my session timed-out. I clicked on a picture and it asked me to login again.

Since I had read the above posts, I went to the main login screen, and logged in again. That fixed it for the rest of my surfing.

When I came to the site today, the site recongnised who I was, so I didn't have to login. The only problem I think it could be is some type of session time-out variable, but I don't know if its a client issue or a server issue.

Whatever it is, it seems to have fixed itself on my machine. Who knows, it might even be a good-old Microsoft Issue. :confused: