[johan]

ok... update... had a server specialist look at this whole thing and they suggest it's due to load balancing. Which kind of makes sense -the site is on 2 separate servers and users will be served the site from either server depending on the load, they may also go from one to the other whilst browsing the site. This becomes a problem when they login and the script stores their session as a php session on the server itself, if they are flicked over to the other server the session is not there and they are asked to login again. This would normally be solved by storing the php sessions in the data base so they are there no matter which server the visitor is on. I take it something like this would be a very extensive rewrite so probably isn't in the roadmap?

Many thanks