Oct 10th, 2011, 2:37 PM
Hey guys,
Okay, yes, it IS an issue, and caused by a weird server-ism. The short answer is that the demo is sandboxed, running on it's own user on the server. When sessions are created on the main site, the demo subdomain is attempting to read them from the other user's sessions storage, causing the error. Clearing sessions on the demo will temporarily fix it, but it'll keep coming back.
I'm looking into a solution now.
- Ben
Okay, yes, it IS an issue, and caused by a weird server-ism. The short answer is that the demo is sandboxed, running on it's own user on the server. When sessions are created on the main site, the demo subdomain is attempting to read them from the other user's sessions storage, causing the error. Clearing sessions on the demo will temporarily fix it, but it'll keep coming back.
I'm looking into a solution now.
- Ben